Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24e14d669afc34276afec3b96df6a1c0f1c70e64ba6471c6278f4f59b46eaa47

Tx prefix hash: dfcc22d6a230e214f446126262c3c8bcb7ef5f4da304752437fca79136222aea
Tx public key: 418d4477fb54404c598be95d5c3ecaa4176ec18f12581da329829f23eba6d33d
Timestamp: 1583849075 Timestamp [UCT]: 2020-03-10 14:04:35 Age [y:d:h:m:s]: 04:359:00:06:49
Block: 79666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151621 RingCT/type: yes/0
Extra: 01418d4477fb54404c598be95d5c3ecaa4176ec18f12581da329829f23eba6d33d0211000000078a2ee0d9000000000000000000

1 output(s) for total of 334.221405724000 dcy

stealth address amount amount idx
00: 3fe1c58e5fd4918dcbf01718cb19ac820528f8386eb78155e17a5c97dd368b94 334.221405724000 145814 of 0

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": 79676, "vin": [ { "gen": { "height": 79666 } } ], "vout": [ { "amount": 334221405724, "target": { "key": "3fe1c58e5fd4918dcbf01718cb19ac820528f8386eb78155e17a5c97dd368b94" } } ], "extra": [ 1, 65, 141, 68, 119, 251, 84, 64, 76, 89, 139, 233, 93, 92, 62, 202, 164, 23, 110, 193, 143, 18, 88, 29, 163, 41, 130, 159, 35, 235, 166, 211, 61, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 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