Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f93aa9864089920bcfd881de067c1201844076c9390297402cc185a793aa162c

Tx prefix hash: 233c0a9038f2fff75a26c2c5d1121a9147cb40ce3563c7eac55c84acaa630448
Tx public key: 1ae9f0fd5c560068d62883cecfdb54e74753a46a9144b70a1b57d5c57035c4c9
Timestamp: 1585420644 Timestamp [UCT]: 2020-03-28 18:37:24 Age [y:d:h:m:s]: 05:069:15:32:26
Block: 89164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1209255 RingCT/type: yes/0
Extra: 011ae9f0fd5c560068d62883cecfdb54e74753a46a9144b70a1b57d5c57035c4c902110000003139be35fb000000000000000000

1 output(s) for total of 310.858989398000 dcy

stealth address amount amount idx
00: a5e3298122445979fcc87d5955acce820247957c01e55e6f37720f13e600b012 310.858989398000 160074 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": 89174, "vin": [ { "gen": { "height": 89164 } } ], "vout": [ { "amount": 310858989398, "target": { "key": "a5e3298122445979fcc87d5955acce820247957c01e55e6f37720f13e600b012" } } ], "extra": [ 1, 26, 233, 240, 253, 92, 86, 0, 104, 214, 40, 131, 206, 207, 219, 84, 231, 71, 83, 164, 106, 145, 68, 183, 10, 27, 87, 213, 197, 112, 53, 196, 201, 2, 17, 0, 0, 0, 49, 57, 190, 53, 251, 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