Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32d2896e8f79a12012ac8611d0896d7780c9a4ecedbe261b8842b54ac2c66e51

Tx prefix hash: b2f87ab4d5eb10a5eed99411371387e479c0775a26e8cf10c48bf5d42f79d8c2
Tx public key: bfb20c8e8a5b5d20d4c22b04452ac4ba581a28d43e5e2a8df08a32b8a9e3cc52
Timestamp: 1764170802 Timestamp [UCT]: 2025-11-26 15:26:42 Age [y:d:h:m:s]: 00:000:19:59:56
Block: 1420627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597 RingCT/type: yes/0
Extra: 01bfb20c8e8a5b5d20d4c22b04452ac4ba581a28d43e5e2a8df08a32b8a9e3cc52021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6eded4361df86ff449ecc45b8fbd95a016f14e4c8c74434a949b6534cc30229 0.600000000000 1909176 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": 1420637, "vin": [ { "gen": { "height": 1420627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6eded4361df86ff449ecc45b8fbd95a016f14e4c8c74434a949b6534cc30229" } } ], "extra": [ 1, 191, 178, 12, 142, 138, 91, 93, 32, 212, 194, 43, 4, 69, 42, 196, 186, 88, 26, 40, 212, 62, 94, 42, 141, 240, 138, 50, 184, 169, 227, 204, 82, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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