Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d83fbaa932c7dd97eb93b2b49293c8922e2cc3c4cd823e690a7e36df5e9dd9cf

Tx prefix hash: f96ce30657b69bbe5d84be1503d22451bd767a255cceaefb860e1c8b95b72247
Tx public key: c5357ff7cd49e4fb915c496c327c9c3d9585b5ae7b82c66c4f0260b74e49150c
Timestamp: 1580115226 Timestamp [UCT]: 2020-01-27 08:53:46 Age [y:d:h:m:s]: 04:354:18:23:39
Block: 53732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1143875 RingCT/type: yes/0
Extra: 01c5357ff7cd49e4fb915c496c327c9c3d9585b5ae7b82c66c4f0260b74e49150c02110000000117786bcf000000000000000000

1 output(s) for total of 407.346891294000 dcy

stealth address amount amount idx
00: 0f1c23e8b0de8fad4dca3281b7ed3685d170e38f87d58379bea0e9731ed96cd5 407.346891294000 99614 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": 53742, "vin": [ { "gen": { "height": 53732 } } ], "vout": [ { "amount": 407346891294, "target": { "key": "0f1c23e8b0de8fad4dca3281b7ed3685d170e38f87d58379bea0e9731ed96cd5" } } ], "extra": [ 1, 197, 53, 127, 247, 205, 73, 228, 251, 145, 92, 73, 108, 50, 124, 156, 61, 149, 133, 181, 174, 123, 130, 198, 108, 79, 2, 96, 183, 78, 73, 21, 12, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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