Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d7cc1d1ad8343c131f5127f673695727db3f5e636aec2fafc151621bc9c331

Tx prefix hash: e8f8aab4fd0b78636dbf19f9f87ee0a74437c8a65b112a704dabc16698d1a725
Tx public key: dd20376fe8f1b484488e644746b55ab880034c4e387a4e467196b04f96b3a9c8
Timestamp: 1750177643 Timestamp [UCT]: 2025-06-17 16:27:23 Age [y:d:h:m:s]: 00:155:14:23:31
Block: 1307064 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109002 RingCT/type: yes/0
Extra: 01dd20376fe8f1b484488e644746b55ab880034c4e387a4e467196b04f96b3a9c8021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 008d64997d9f00a1a5e8d8be31294c1a5d811b26c5bac361062d15f646763c17 0.600000000000 1794673 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": 1307074, "vin": [ { "gen": { "height": 1307064 } } ], "vout": [ { "amount": 600000000, "target": { "key": "008d64997d9f00a1a5e8d8be31294c1a5d811b26c5bac361062d15f646763c17" } } ], "extra": [ 1, 221, 32, 55, 111, 232, 241, 180, 132, 72, 142, 100, 71, 70, 181, 90, 184, 128, 3, 76, 78, 56, 122, 78, 70, 113, 150, 176, 79, 150, 179, 169, 200, 2, 17, 0, 0, 0, 5, 191, 81, 178, 162, 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