Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f71eebf5e71d32b0ee5030353feb14dd71a32a0b165a5d296697017d718e92f

Tx prefix hash: 32de0bd8687d1c9e288979dff03c8831ecd175f26aaa3881bc507189d21d0bcf
Tx public key: 670b0cee2f96238f91b7cde4c7f3164ba08d2d932edc5dd2b1d860dbe3e3be92
Timestamp: 1740116161 Timestamp [UCT]: 2025-02-21 05:36:01 Age [y:d:h:m:s]: 00:229:02:15:46
Block: 1223852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161454 RingCT/type: yes/0
Extra: 01670b0cee2f96238f91b7cde4c7f3164ba08d2d932edc5dd2b1d860dbe3e3be92021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a705d5c084d9d3cc03efcf50ab826d235e26a788c2756674457388f96f1ae72f 0.600000000000 1710709 of 15

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": 1223862, "vin": [ { "gen": { "height": 1223852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a705d5c084d9d3cc03efcf50ab826d235e26a788c2756674457388f96f1ae72f" } } ], "extra": [ 1, 103, 11, 12, 238, 47, 150, 35, 143, 145, 183, 205, 228, 199, 243, 22, 75, 160, 141, 45, 147, 46, 220, 93, 210, 177, 216, 96, 219, 227, 227, 190, 146, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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