Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72ff7f9b6054833e7c6296f648e4e62cd627302731324b2a794a69cbe62c1bdc

Tx prefix hash: 7ca58e8b0b927c25fda841229b4717fdf90d9441883e4f10fe27ae8423c86750
Tx public key: 289b60ed1fe3e93cbe5775fe97f7c78038609ae43e0461f65fdc3c5b46366b9f
Timestamp: 1649573399 Timestamp [UCT]: 2022-04-10 06:49:59 Age [y:d:h:m:s]: 02:339:16:45:58
Block: 477104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762348 RingCT/type: yes/0
Extra: 01289b60ed1fe3e93cbe5775fe97f7c78038609ae43e0461f65fdc3c5b46366b9f021100000011bf7ee4e7000000000000000000

1 output(s) for total of 16.112266321000 dcy

stealth address amount amount idx
00: 78b2f275aecd7955e2efd8ddd3717e2a35dad3cd4f9b9f5427e1bf5ddd6b9ea7 16.112266321000 897727 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": 477114, "vin": [ { "gen": { "height": 477104 } } ], "vout": [ { "amount": 16112266321, "target": { "key": "78b2f275aecd7955e2efd8ddd3717e2a35dad3cd4f9b9f5427e1bf5ddd6b9ea7" } } ], "extra": [ 1, 40, 155, 96, 237, 31, 227, 233, 60, 190, 87, 117, 254, 151, 247, 199, 128, 56, 96, 154, 228, 62, 4, 97, 246, 95, 220, 60, 91, 70, 54, 107, 159, 2, 17, 0, 0, 0, 17, 191, 126, 228, 231, 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