Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: a0c07f8b9d832b92aa6a19906cf383b7ca2571c8cf04e9892716fba0452fa38d

Tx prefix hash: a70bcaee0d9d3679d71f1a65370450a21e96b1806e9f303d4479274526846e91
Tx public key: ae8ef87807c5042ac631575e19ffc0f1624cb3f44e51c4a61e9aa839b312010b
Timestamp: 1759197382 Timestamp [UCT]: 2025-09-30 01:56:22 Age [y:d:h:m:s]: 00:041:18:59:39
Block: 1379395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29937 RingCT/type: yes/0
Extra: 01ae8ef87807c5042ac631575e19ffc0f1624cb3f44e51c4a61e9aa839b312010b021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e28c2fb176831251b0208bf71950e2e6bb0454bf9e3e33709559d3179c413f4 0.600000000000 1867492 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1379405, "vin": [ { "gen": { "height": 1379395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e28c2fb176831251b0208bf71950e2e6bb0454bf9e3e33709559d3179c413f4" } } ], "extra": [ 1, 174, 142, 248, 120, 7, 197, 4, 42, 198, 49, 87, 94, 25, 255, 192, 241, 98, 76, 179, 244, 78, 81, 196, 166, 30, 154, 168, 57, 179, 18, 1, 11, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8