Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c981d6ae7f62d940f877c7c507b6d61b95499ffe15aed78c6c97bcea8be84a4a

Tx prefix hash: c3bb65f4ba7949c5eb8c06857fa2eee4cc97dfca99d5f5668962db2cd1029b1c
Tx public key: 1de9d5b80d15971533f941fd5932da9dc7ffd610710de73cfc30085a025ccf76
Timestamp: 1582935259 Timestamp [UCT]: 2020-02-29 00:14:19 Age [y:d:h:m:s]: 04:300:13:31:06
Block: 73696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108497 RingCT/type: yes/0
Extra: 011de9d5b80d15971533f941fd5932da9dc7ffd610710de73cfc30085a025ccf7602110000000f8a2ee0d9000000000000000000

1 output(s) for total of 349.796418510000 dcy

stealth address amount amount idx
00: e43e1f4b536af51e64be4adcfe8425987a60d6ba9e1a5fe4debd7855c6a42a9b 349.796418510000 136013 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": 73706, "vin": [ { "gen": { "height": 73696 } } ], "vout": [ { "amount": 349796418510, "target": { "key": "e43e1f4b536af51e64be4adcfe8425987a60d6ba9e1a5fe4debd7855c6a42a9b" } } ], "extra": [ 1, 29, 233, 213, 184, 13, 21, 151, 21, 51, 249, 65, 253, 89, 50, 218, 157, 199, 255, 214, 16, 113, 13, 231, 60, 252, 48, 8, 90, 2, 92, 207, 118, 2, 17, 0, 0, 0, 15, 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