Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f431aa4542001e8a87a196eb70a204d5eac3b664cb3542532c2e05fbfed79fb9

Tx prefix hash: 6b9003eb79ebfb78259fda9012907705ae418215e216a9de860f3510c232f238
Tx public key: 17f6e51f4448824d70c13e6a478436f8d879d6e2f9dcb9fb6da09fa69321dfba
Timestamp: 1748170025 Timestamp [UCT]: 2025-05-25 10:47:05 Age [y:d:h:m:s]: 00:179:11:40:54
Block: 1290564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125966 RingCT/type: yes/0
Extra: 0117f6e51f4448824d70c13e6a478436f8d879d6e2f9dcb9fb6da09fa69321dfba0211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76e0faf6865617c7bede1faf5d87539177e40065a7b7738fdb3762f5dc25d32e 0.600000000000 1778033 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": 1290574, "vin": [ { "gen": { "height": 1290564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76e0faf6865617c7bede1faf5d87539177e40065a7b7738fdb3762f5dc25d32e" } } ], "extra": [ 1, 23, 246, 229, 31, 68, 72, 130, 77, 112, 193, 62, 106, 71, 132, 54, 248, 216, 121, 214, 226, 249, 220, 185, 251, 109, 160, 159, 166, 147, 33, 223, 186, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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