Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40b342d03e819a95c023211a80a8eb2feaa21d30f37c2d4b778f2e5b7991e4a3

Tx prefix hash: a3ea79be6a3678d78e93a8721080a6a389e992196e32d0536829e4cdfa316fc7
Tx public key: 3ac2d2fbae1dd10846639f80d7def503e5d621be01f2e8c351954b333e363c2c
Timestamp: 1762707398 Timestamp [UCT]: 2025-11-09 16:56:38 Age [y:d:h:m:s]: 00:055:03:40:52
Block: 1408502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39499 RingCT/type: yes/0
Extra: 013ac2d2fbae1dd10846639f80d7def503e5d621be01f2e8c351954b333e363c2c0211000000048368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aabbfe064595466380685e9b54f3228dca643dd98955d712dd2638fca0e25c8b 0.600000000000 1896931 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": 1408512, "vin": [ { "gen": { "height": 1408502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aabbfe064595466380685e9b54f3228dca643dd98955d712dd2638fca0e25c8b" } } ], "extra": [ 1, 58, 194, 210, 251, 174, 29, 209, 8, 70, 99, 159, 128, 215, 222, 245, 3, 229, 214, 33, 190, 1, 242, 232, 195, 81, 149, 75, 51, 62, 54, 60, 44, 2, 17, 0, 0, 0, 4, 131, 104, 38, 109, 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