Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03104df33d2ec8c0cd3ed98a1f516389b8bf8136f771761afe9a6d84fef79061

Tx prefix hash: c775334262b3c42caf35daeab7cc00efb1f5765f687fbda1b17a05d66651a6e5
Tx public key: 6d21ae657358c4ea5d53994cdfa219623efb1cb2201b4f97a85ab58343f2e8f2
Timestamp: 1762008367 Timestamp [UCT]: 2025-11-01 14:46:07 Age [y:d:h:m:s]: 00:005:16:53:59
Block: 1402732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4058 RingCT/type: yes/0
Extra: 016d21ae657358c4ea5d53994cdfa219623efb1cb2201b4f97a85ab58343f2e8f202110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d899733c9927551a0db75abb6217e6a1fa11c4a7222c27f16f84d8223de41c6 0.600000000000 1891051 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": 1402742, "vin": [ { "gen": { "height": 1402732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d899733c9927551a0db75abb6217e6a1fa11c4a7222c27f16f84d8223de41c6" } } ], "extra": [ 1, 109, 33, 174, 101, 115, 88, 196, 234, 93, 83, 153, 76, 223, 162, 25, 98, 62, 251, 28, 178, 32, 27, 79, 151, 168, 90, 181, 131, 67, 242, 232, 242, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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