Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2ccd56fed588b12f9cc49453c07fcc46528e84d8d921921d484881b0dc0fa3d

Tx prefix hash: 6b07293a4c0aec04e030100279b99e04b1dd048534695a6f16971ea7d8b49638
Tx public key: a74989e5e0af415f0712245a4dcc6f8fbe12f4095a275fa708e534395fc7ad60
Timestamp: 1710666961 Timestamp [UCT]: 2024-03-17 09:16:01 Age [y:d:h:m:s]: 01:229:01:43:54
Block: 980199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422421 RingCT/type: yes/0
Extra: 01a74989e5e0af415f0712245a4dcc6f8fbe12f4095a275fa708e534395fc7ad600211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82cb5538d3b1a3b347a3fb08e9204a9451d9333d093799a6dbfcdad3871a42c4 0.600000000000 1440258 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": 980209, "vin": [ { "gen": { "height": 980199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82cb5538d3b1a3b347a3fb08e9204a9451d9333d093799a6dbfcdad3871a42c4" } } ], "extra": [ 1, 167, 73, 137, 229, 224, 175, 65, 95, 7, 18, 36, 90, 77, 204, 111, 143, 190, 18, 244, 9, 90, 39, 95, 167, 8, 229, 52, 57, 95, 199, 173, 96, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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