Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5b424436ca665613f5ce7dc24a420adf93e2e08102b8996c06a6ddb960b5d3c

Tx prefix hash: 78bd959776029e32dc86c09bd4a089a6e52efa5c905b28ddf9ebfc816b457d56
Tx public key: cf111eea6268951f39e9a2b85727822fcead1e79e245529f7bacf6390f25e87a
Timestamp: 1722714984 Timestamp [UCT]: 2024-08-03 19:56:24 Age [y:d:h:m:s]: 00:248:02:34:46
Block: 1080057 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177218 RingCT/type: yes/0
Extra: 01cf111eea6268951f39e9a2b85727822fcead1e79e245529f7bacf6390f25e87a021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0b1567de161f6a1b03bb32cfd8cc4d8a3c3be2d5e942ecfba8255dbed516810 0.600000000000 1553270 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": 1080067, "vin": [ { "gen": { "height": 1080057 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0b1567de161f6a1b03bb32cfd8cc4d8a3c3be2d5e942ecfba8255dbed516810" } } ], "extra": [ 1, 207, 17, 30, 234, 98, 104, 149, 31, 57, 233, 162, 184, 87, 39, 130, 47, 206, 173, 30, 121, 226, 69, 82, 159, 123, 172, 246, 57, 15, 37, 232, 122, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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