Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f7649c4eb7deeb3a3f46be15b9021e0f67bffa2a12b8f9f6e8879e2ace9ba5

Tx prefix hash: 5be57bf69b3bd39f8168ee0908432cf92bd6812b45ea69d8f8d3a4e5dcab593e
Tx public key: ad24d67366fee96a53c6edfd70de14cb56d706181428c565c49b7fa4deb2f65c
Timestamp: 1728777350 Timestamp [UCT]: 2024-10-12 23:55:50 Age [y:d:h:m:s]: 00:167:05:36:07
Block: 1130333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119287 RingCT/type: yes/0
Extra: 01ad24d67366fee96a53c6edfd70de14cb56d706181428c565c49b7fa4deb2f65c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5dea4015372e13351d0abc5da582d23839a5fa56b83c98d9affebcbf570a389 0.600000000000 1613208 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": 1130343, "vin": [ { "gen": { "height": 1130333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5dea4015372e13351d0abc5da582d23839a5fa56b83c98d9affebcbf570a389" } } ], "extra": [ 1, 173, 36, 214, 115, 102, 254, 233, 106, 83, 198, 237, 253, 112, 222, 20, 203, 86, 215, 6, 24, 20, 40, 197, 101, 196, 155, 127, 164, 222, 178, 246, 92, 2, 17, 0, 0, 0, 2, 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