Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b7ab8b9efaca399091e0c2c1a7c0a70f81cb595498813e3a935af5c7ba6dec3

Tx prefix hash: 1890d0934c909be5100fe162da048ba8272dffad353c5d3497ac209d9393ddae
Tx public key: a550ee82efc64333a2bd2534d8e7e1547ef3233e12d1f72a81e115a2c2615fd5
Timestamp: 1724925213 Timestamp [UCT]: 2024-08-29 09:53:33 Age [y:d:h:m:s]: 00:238:12:27:03
Block: 1098386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170341 RingCT/type: yes/0
Extra: 01a550ee82efc64333a2bd2534d8e7e1547ef3233e12d1f72a81e115a2c2615fd502110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d32229cebd6a8a9e0277d955837e246823a9ccd16e7a9c090d48fc29856d50 0.600000000000 1574083 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": 1098396, "vin": [ { "gen": { "height": 1098386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d32229cebd6a8a9e0277d955837e246823a9ccd16e7a9c090d48fc29856d50" } } ], "extra": [ 1, 165, 80, 238, 130, 239, 198, 67, 51, 162, 189, 37, 52, 216, 231, 225, 84, 126, 243, 35, 62, 18, 209, 247, 42, 129, 225, 21, 162, 194, 97, 95, 213, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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