Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92580f518743d0981ff9f684b3eb188524eb664622480420f6083a5ecbca4ecb

Tx prefix hash: d912a66ca52600795d0b14c0acb7b2f0d5ecc0e536afed368158b2eb7db8c0c2
Tx public key: 8117551d9bc75c7f3da0e98e3fd84b571e4c3f50813b1ed94208d8d0a5474d62
Timestamp: 1726627812 Timestamp [UCT]: 2024-09-18 02:50:12 Age [y:d:h:m:s]: 00:253:02:15:39
Block: 1112490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180770 RingCT/type: yes/0
Extra: 018117551d9bc75c7f3da0e98e3fd84b571e4c3f50813b1ed94208d8d0a5474d6202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beaf0464ac788aed0003404d0eeee14b7a2997010d94fb30c13e3fbb4f0226f7 0.600000000000 1591831 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": 1112500, "vin": [ { "gen": { "height": 1112490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beaf0464ac788aed0003404d0eeee14b7a2997010d94fb30c13e3fbb4f0226f7" } } ], "extra": [ 1, 129, 23, 85, 29, 155, 199, 92, 127, 61, 160, 233, 142, 63, 216, 75, 87, 30, 76, 63, 80, 129, 59, 30, 217, 66, 8, 216, 208, 165, 71, 77, 98, 2, 17, 0, 0, 0, 4, 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