Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c12b4299aa6b7e2e7c247ac189725085d0d89a6daefb44bd1a48c1d0d464f3

Tx prefix hash: 8247627c8620817030bcabe41b824f002e016229f5f4dd53054cc9b9ae5ea1cb
Tx public key: 43cbffbba0c40f5ef9baded79a020d790cdad3fc9ecde5026b5413ee59f2ce53
Timestamp: 1582444136 Timestamp [UCT]: 2020-02-23 07:48:56 Age [y:d:h:m:s]: 04:304:15:46:44
Block: 70858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110225 RingCT/type: yes/0
Extra: 0143cbffbba0c40f5ef9baded79a020d790cdad3fc9ecde5026b5413ee59f2ce5302110000000203d36d11000000000000000000

1 output(s) for total of 357.452907439000 dcy

stealth address amount amount idx
00: b69e66f49eeda99cbccccbfa78ea163e45f4e883fc80fc4a07a2eadb38e364a6 357.452907439000 130888 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": 70868, "vin": [ { "gen": { "height": 70858 } } ], "vout": [ { "amount": 357452907439, "target": { "key": "b69e66f49eeda99cbccccbfa78ea163e45f4e883fc80fc4a07a2eadb38e364a6" } } ], "extra": [ 1, 67, 203, 255, 187, 160, 196, 15, 94, 249, 186, 222, 215, 154, 2, 13, 121, 12, 218, 211, 252, 158, 205, 229, 2, 107, 84, 19, 238, 89, 242, 206, 83, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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