Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d96f84c4983d092ae33fe7f6533702bf6753c122354e4eb20094dd503bf4fd8c

Tx prefix hash: 8b40b223c488c2102568765c1634da6865b6fdcce6fdcf6636fc07efcb70e9d5
Tx public key: 1fb9195fd71bee640ad3b453f1e514e96dd31c2df111e4d2129c1128a969dbb6
Timestamp: 1617148565 Timestamp [UCT]: 2021-03-30 23:56:05 Age [y:d:h:m:s]: 03:271:21:05:58
Block: 230033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 953801 RingCT/type: yes/0
Extra: 011fb9195fd71bee640ad3b453f1e514e96dd31c2df111e4d2129c1128a969dbb60211000000a090ec05ad000000000000000000

1 output(s) for total of 106.122081885000 dcy

stealth address amount amount idx
00: 0265679bb04759833d667ed189a35b3c0fb9a37fc89575e96916eb33db17c4a0 106.122081885000 477381 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": 230043, "vin": [ { "gen": { "height": 230033 } } ], "vout": [ { "amount": 106122081885, "target": { "key": "0265679bb04759833d667ed189a35b3c0fb9a37fc89575e96916eb33db17c4a0" } } ], "extra": [ 1, 31, 185, 25, 95, 215, 27, 238, 100, 10, 211, 180, 83, 241, 229, 20, 233, 109, 211, 28, 45, 241, 17, 228, 210, 18, 156, 17, 40, 169, 105, 219, 182, 2, 17, 0, 0, 0, 160, 144, 236, 5, 173, 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