Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94cbbc386830638641596e6508f037d60d17da07c3580ccfd534e7ecf74fde03

Tx prefix hash: a00299377248163318762c96a74b78a588e8b91715b443fcd8da245315cb694e
Tx public key: cb2b8edd8eca9e27302b5e299aac7b7da0b1449f9e32ed50073ddd6a446195c6
Timestamp: 1721089987 Timestamp [UCT]: 2024-07-16 00:33:07 Age [y:d:h:m:s]: 00:265:14:43:30
Block: 1066604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189746 RingCT/type: yes/0
Extra: 01cb2b8edd8eca9e27302b5e299aac7b7da0b1449f9e32ed50073ddd6a446195c6021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae07144a3b53dd37abc33733d5e4af4677d4fb70bf2db0d7faf7124fedc7d76d 0.600000000000 1537271 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": 1066614, "vin": [ { "gen": { "height": 1066604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae07144a3b53dd37abc33733d5e4af4677d4fb70bf2db0d7faf7124fedc7d76d" } } ], "extra": [ 1, 203, 43, 142, 221, 142, 202, 158, 39, 48, 43, 94, 41, 154, 172, 123, 125, 160, 177, 68, 159, 158, 50, 237, 80, 7, 61, 221, 106, 68, 97, 149, 198, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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