Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17876ba67c59f521040ed5d93cfe78495d63f9c476129f0310dcbd11accef197

Tx prefix hash: 9436674e52a29e7719da2428b0877708cac5eda794c482236fb62e48964781be
Tx public key: a057a2f1b7b6b5a0d75ea2f63b14a831d28a3801fee96b630e110751f42c1190
Timestamp: 1723569215 Timestamp [UCT]: 2024-08-13 17:13:35 Age [y:d:h:m:s]: 00:247:14:31:55
Block: 1087151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176850 RingCT/type: yes/0
Extra: 01a057a2f1b7b6b5a0d75ea2f63b14a831d28a3801fee96b630e110751f42c119002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95b9c5a2bdffe1bcddfb8dcf5b56e703c3b4be84410f247a009ff7bebb7d8be3 0.600000000000 1561756 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": 1087161, "vin": [ { "gen": { "height": 1087151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95b9c5a2bdffe1bcddfb8dcf5b56e703c3b4be84410f247a009ff7bebb7d8be3" } } ], "extra": [ 1, 160, 87, 162, 241, 183, 182, 181, 160, 215, 94, 162, 246, 59, 20, 168, 49, 210, 138, 56, 1, 254, 233, 107, 99, 14, 17, 7, 81, 244, 44, 17, 144, 2, 17, 0, 0, 0, 5, 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