Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57c91f1352f4855ebdb057f59a9fc10da367f482215b4f31185220edbf6b79af

Tx prefix hash: 35952409221d32cb2e2dd87a304641fe39cdd81a7eebbed6e952288bea7e63e8
Tx public key: 3f94d0a1e8c7f057e2d2bb653840be46bbff94c29b8a33df609b7ee7fdafed93
Timestamp: 1736704664 Timestamp [UCT]: 2025-01-12 17:57:44 Age [y:d:h:m:s]: 00:311:20:32:25
Block: 1195905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220383 RingCT/type: yes/0
Extra: 013f94d0a1e8c7f057e2d2bb653840be46bbff94c29b8a33df609b7ee7fdafed930211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d43c5969a4b2f8974e9cd0b74581cd1708f206a65fb03df9326c6fa5164d5700 0.600000000000 1682498 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": 1195915, "vin": [ { "gen": { "height": 1195905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d43c5969a4b2f8974e9cd0b74581cd1708f206a65fb03df9326c6fa5164d5700" } } ], "extra": [ 1, 63, 148, 208, 161, 232, 199, 240, 87, 226, 210, 187, 101, 56, 64, 190, 70, 187, 255, 148, 194, 155, 138, 51, 223, 96, 155, 126, 231, 253, 175, 237, 147, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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