Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72bc4a8cbf3744e9262f3c889715f12d8ac0f8e612b9617ada30b49e05d509c5

Tx prefix hash: 6198482afa4c1f557afb7c10eb34020b2e22014c22f4c6948e57e5e3b3a02d72
Tx public key: d0b212411a4787998265b42162d146ab48d162c276394ea4c2e53ec548c9af42
Timestamp: 1752211510 Timestamp [UCT]: 2025-07-11 05:25:10 Age [y:d:h:m:s]: 00:138:11:29:39
Block: 1323070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97607 RingCT/type: yes/0
Extra: 01d0b212411a4787998265b42162d146ab48d162c276394ea4c2e53ec548c9af42021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef905e31ab040fb20543beb7b4da43e9ec11db670216e5cf3e704ff0ade5f617 0.600000000000 1810805 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": 1323080, "vin": [ { "gen": { "height": 1323070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef905e31ab040fb20543beb7b4da43e9ec11db670216e5cf3e704ff0ade5f617" } } ], "extra": [ 1, 208, 178, 18, 65, 26, 71, 135, 153, 130, 101, 180, 33, 98, 209, 70, 171, 72, 209, 98, 194, 118, 57, 78, 164, 194, 229, 62, 197, 72, 201, 175, 66, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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