Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16370fb49110dd0ad2e82f7ef975a9243b75e2b796824f7644ee161a65ec71f2

Tx prefix hash: bd845b415ebadd1373c8e23ac885b6508b5e203e716f65cf306225d1541f995f
Tx public key: 3f49cad7d216b1e3f8408d69c3adc3354c2f1fb1c322facd80cc1f7dc6f29e97
Timestamp: 1764622404 Timestamp [UCT]: 2025-12-01 20:53:24 Age [y:d:h:m:s]: 00:035:00:10:27
Block: 1424361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25087 RingCT/type: yes/0
Extra: 013f49cad7d216b1e3f8408d69c3adc3354c2f1fb1c322facd80cc1f7dc6f29e970211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70eb85fb97e644f8b479bbf59b5f64a950bff2cc2b51b7464e87a7085c55a3c6 0.600000000000 1912992 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": 1424371, "vin": [ { "gen": { "height": 1424361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70eb85fb97e644f8b479bbf59b5f64a950bff2cc2b51b7464e87a7085c55a3c6" } } ], "extra": [ 1, 63, 73, 202, 215, 210, 22, 177, 227, 248, 64, 141, 105, 195, 173, 195, 53, 76, 47, 31, 177, 195, 34, 250, 205, 128, 204, 31, 125, 198, 242, 158, 151, 2, 17, 0, 0, 0, 2, 140, 235, 127, 9, 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