Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbdbd61ddef888cb118d520a79137776c390a259500fc1985a3c2c4d993b16af

Tx prefix hash: 89cbd2ed25784804b5424fce7e9d7cdb68478d04597cf212de3c4df39cc8c67f
Tx public key: 6d1fa3ab1e8a8b3ca581c8add05dcfe411756993f81e71af9bdd328da2a9d1fc
Timestamp: 1750890765 Timestamp [UCT]: 2025-06-25 22:32:45 Age [y:d:h:m:s]: 00:146:21:57:38
Block: 1312778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102984 RingCT/type: yes/0
Extra: 016d1fa3ab1e8a8b3ca581c8add05dcfe411756993f81e71af9bdd328da2a9d1fc021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f9904219d01859b4f08579bd466c97fc6fde059f8ab3e101213cf6c334d119 0.600000000000 1800413 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": 1312788, "vin": [ { "gen": { "height": 1312778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f9904219d01859b4f08579bd466c97fc6fde059f8ab3e101213cf6c334d119" } } ], "extra": [ 1, 109, 31, 163, 171, 30, 138, 139, 60, 165, 129, 200, 173, 208, 93, 207, 228, 17, 117, 105, 147, 248, 30, 113, 175, 155, 221, 50, 141, 162, 169, 209, 252, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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