Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30736f0a1d78d57f656aa8a5ff84c3e323f62894edebdc66d67ceb9e5e7b16e5

Tx prefix hash: ab4798d23467fe4e2291d0fb5e4ba03eb91194b5876ae7c6c41cf7b8c79ce0db
Tx public key: 8442772ebc2abe2d60bf4fc56e435f7d07afb13262a26befc27cdf5e1d1dddce
Timestamp: 1716663743 Timestamp [UCT]: 2024-05-25 19:02:23 Age [y:d:h:m:s]: 01:167:15:48:50
Block: 1029906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378411 RingCT/type: yes/0
Extra: 018442772ebc2abe2d60bf4fc56e435f7d07afb13262a26befc27cdf5e1d1dddce0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6604233414b5df501e789f7876f16e393aa831ddc2067c09437288e8be348253 0.600000000000 1498121 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": 1029916, "vin": [ { "gen": { "height": 1029906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6604233414b5df501e789f7876f16e393aa831ddc2067c09437288e8be348253" } } ], "extra": [ 1, 132, 66, 119, 46, 188, 42, 190, 45, 96, 191, 79, 197, 110, 67, 95, 125, 7, 175, 177, 50, 98, 162, 107, 239, 194, 124, 223, 94, 29, 29, 221, 206, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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