Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c158bf7af971f47c5ca1b278b6a1040e7d331ccc624a813f0a1b7ff91cbd64

Tx prefix hash: 47736b134e9278c2ed3205acbf4304ecd2fdc0f07a3550e962823f892c1c1867
Tx public key: 0adc805901f17ff57d50e453260b1ebb1e17a703d8e6fad3cefea5c819c92ee4
Timestamp: 1664571600 Timestamp [UCT]: 2022-09-30 21:00:00 Age [y:d:h:m:s]: 02:046:01:12:12
Block: 599146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554676 RingCT/type: yes/0
Extra: 010adc805901f17ff57d50e453260b1ebb1e17a703d8e6fad3cefea5c819c92ee4021100000005faf35c9c000000000000000000

1 output(s) for total of 6.350101187000 dcy

stealth address amount amount idx
00: 215971eb454675450b1a0e35ba78611374ea2c345c3e79aac80e76a67c92ea19 6.350101187000 1035017 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": 599156, "vin": [ { "gen": { "height": 599146 } } ], "vout": [ { "amount": 6350101187, "target": { "key": "215971eb454675450b1a0e35ba78611374ea2c345c3e79aac80e76a67c92ea19" } } ], "extra": [ 1, 10, 220, 128, 89, 1, 241, 127, 245, 125, 80, 228, 83, 38, 11, 30, 187, 30, 23, 167, 3, 216, 230, 250, 211, 206, 254, 165, 200, 25, 201, 46, 228, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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