Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1615ae8949add400e67c8ec23b638d0816535d5c451240822000e6339ea414d

Tx prefix hash: 133e0fc11f01e14afd2ebeaa39f967b84537e815607b5f4116474171a5480e4f
Tx public key: 53325ea2e85b5795496224e224c433621db45c7a5043e6cf733733ed96ea3f14
Timestamp: 1578831580 Timestamp [UCT]: 2020-01-12 12:19:40 Age [y:d:h:m:s]: 04:348:00:37:44
Block: 43935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1138238 RingCT/type: yes/0
Extra: 0153325ea2e85b5795496224e224c433621db45c7a5043e6cf733733ed96ea3f14021100000037b221b3d1000000000000000000

1 output(s) for total of 438.961012153000 dcy

stealth address amount amount idx
00: d396a8ed075368e4995c0b975ea0723810ece03547e92571135d0d9622dc6050 438.961012153000 79765 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": 43945, "vin": [ { "gen": { "height": 43935 } } ], "vout": [ { "amount": 438961012153, "target": { "key": "d396a8ed075368e4995c0b975ea0723810ece03547e92571135d0d9622dc6050" } } ], "extra": [ 1, 83, 50, 94, 162, 232, 91, 87, 149, 73, 98, 36, 226, 36, 196, 51, 98, 29, 180, 92, 122, 80, 67, 230, 207, 115, 55, 51, 237, 150, 234, 63, 20, 2, 17, 0, 0, 0, 55, 178, 33, 179, 209, 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