Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d50109f3770b37f5718b9b1ec2c1e24c22707849e470d03fd63a581bc52b0360

Tx prefix hash: 40c2d9cdabd26f47d23bbfd1bd879b6f5a8d6263080d09e5757573d7986ca477
Tx public key: 572177e8b068d1820e5773aae496452ee515c427ee44dfbff3ce4c0dab0da837
Timestamp: 1580115169 Timestamp [UCT]: 2020-01-27 08:52:49 Age [y:d:h:m:s]: 05:038:01:09:05
Block: 53730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178145 RingCT/type: yes/0
Extra: 01572177e8b068d1820e5773aae496452ee515c427ee44dfbff3ce4c0dab0da8370211000000022264afe6000000000000000000

1 output(s) for total of 407.360136985000 dcy

stealth address amount amount idx
00: 5a1de25515542feea1b71650d8b44de33318bece7b58de8f523e8dea73b033f2 407.360136985000 99610 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": 53740, "vin": [ { "gen": { "height": 53730 } } ], "vout": [ { "amount": 407360136985, "target": { "key": "5a1de25515542feea1b71650d8b44de33318bece7b58de8f523e8dea73b033f2" } } ], "extra": [ 1, 87, 33, 119, 232, 176, 104, 209, 130, 14, 87, 115, 170, 228, 150, 69, 46, 229, 21, 196, 39, 238, 68, 223, 191, 243, 206, 76, 13, 171, 13, 168, 55, 2, 17, 0, 0, 0, 2, 34, 100, 175, 230, 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