Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 052c62c7aefd69bf264d6d3c4a9fd35d1f77384ce13964d3e1c06ab43bd7f105

Tx prefix hash: 2f38e2001a6f55bbfc726638313f7e805633b1eabc02a0b868e599260dcdac74
Tx public key: f1e0b64c96f8eff758056d99bea2ee2ab51e239da17b7e282a3cd107563fca86
Timestamp: 1757773349 Timestamp [UCT]: 2025-09-13 14:22:29 Age [y:d:h:m:s]: 00:101:11:33:37
Block: 1367602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72660 RingCT/type: yes/0
Extra: 01f1e0b64c96f8eff758056d99bea2ee2ab51e239da17b7e282a3cd107563fca86021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1b544c79ec98b98d1bfa23d67ec1603a42f04eba9317a0c179775fbbb382af5 0.600000000000 1855641 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": 1367612, "vin": [ { "gen": { "height": 1367602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1b544c79ec98b98d1bfa23d67ec1603a42f04eba9317a0c179775fbbb382af5" } } ], "extra": [ 1, 241, 224, 182, 76, 150, 248, 239, 247, 88, 5, 109, 153, 190, 162, 238, 42, 181, 30, 35, 157, 161, 123, 126, 40, 42, 60, 209, 7, 86, 63, 202, 134, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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