Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 831ef7cf4f195d737f60a9fef2a9cc6f43bd24f79bde88a104a21b87692470b3

Tx prefix hash: 8df4bb644f91aeb6f0b1620af927dfb95b71da45ef1c25abf8a5e422c1a3323b
Tx public key: 192c6f2c8661bdcd4175668ace278c96fcb657987103ee0d0ab45fafbcd123f4
Timestamp: 1577562693 Timestamp [UCT]: 2019-12-28 19:51:33 Age [y:d:h:m:s]: 04:188:11:21:49
Block: 33783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1023695 RingCT/type: yes/0
Extra: 01192c6f2c8661bdcd4175668ace278c96fcb657987103ee0d0ab45fafbcd123f402110000008778873133000000000000000000

1 output(s) for total of 474.311608353000 dcy

stealth address amount amount idx
00: a6d39c422eab2c594578e0d7aedd35f81c7a6d480dc0f4f51a46b930ee104200 474.311608353000 56676 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": 33793, "vin": [ { "gen": { "height": 33783 } } ], "vout": [ { "amount": 474311608353, "target": { "key": "a6d39c422eab2c594578e0d7aedd35f81c7a6d480dc0f4f51a46b930ee104200" } } ], "extra": [ 1, 25, 44, 111, 44, 134, 97, 189, 205, 65, 117, 102, 138, 206, 39, 140, 150, 252, 182, 87, 152, 113, 3, 238, 13, 10, 180, 95, 175, 188, 209, 35, 244, 2, 17, 0, 0, 0, 135, 120, 135, 49, 51, 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