Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f754dec381ca4259fb9cc19c357bf6d5eb7ef31dd734f8995f1912583350c93

Tx prefix hash: 29bb897b2a68421ad9340126efc7e350dd36c5ce485a9a14ac1403b9014e73a3
Tx public key: 31e77d3b68ad93c8b6302ad1833a25eb94020d88425af4ed308595ea1663f7aa
Timestamp: 1577822345 Timestamp [UCT]: 2019-12-31 19:59:05 Age [y:d:h:m:s]: 04:359:03:33:33
Block: 35983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1145798 RingCT/type: yes/0
Extra: 0131e77d3b68ad93c8b6302ad1833a25eb94020d88425af4ed308595ea1663f7aa0211000000298a2ee0d9000000000000000000

1 output(s) for total of 466.416856120000 dcy

stealth address amount amount idx
00: afedccb0425d062c4e006e6d3f95fca2621c083e783b2585c2a3bd68f263202d 466.416856120000 60791 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": 35993, "vin": [ { "gen": { "height": 35983 } } ], "vout": [ { "amount": 466416856120, "target": { "key": "afedccb0425d062c4e006e6d3f95fca2621c083e783b2585c2a3bd68f263202d" } } ], "extra": [ 1, 49, 231, 125, 59, 104, 173, 147, 200, 182, 48, 42, 209, 131, 58, 37, 235, 148, 2, 13, 136, 66, 90, 244, 237, 48, 133, 149, 234, 22, 99, 247, 170, 2, 17, 0, 0, 0, 41, 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