Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f6a3bba622fefd60315aeab220beb16413eb0614f73059fc97f4b1efe067e1

Tx prefix hash: d946240c7e1ef5efa92549a60d7a02f5b07a211cad0e756e30a0a04db5a168f9
Tx public key: dda49573f8a38fa9b4f64c7b04e1843a472d22df8924dd825fea5a4988f25955
Timestamp: 1731368284 Timestamp [UCT]: 2024-11-11 23:38:04 Age [y:d:h:m:s]: 00:017:09:47:13
Block: 1151702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12475 RingCT/type: yes/0
Extra: 01dda49573f8a38fa9b4f64c7b04e1843a472d22df8924dd825fea5a4988f259550211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59cb0c341060bd33d316c5b7e3be8e6cd47a0b76778875558cd31ba75a03fe31 0.600000000000 1637283 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": 1151712, "vin": [ { "gen": { "height": 1151702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59cb0c341060bd33d316c5b7e3be8e6cd47a0b76778875558cd31ba75a03fe31" } } ], "extra": [ 1, 221, 164, 149, 115, 248, 163, 143, 169, 180, 246, 76, 123, 4, 225, 132, 58, 71, 45, 34, 223, 137, 36, 221, 130, 95, 234, 90, 73, 136, 242, 89, 85, 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