Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5deecf48b3a75b32686df56e4126ed202390d168883811314827f0a82abb44a

Tx prefix hash: 7d26642117ddf262f7c0d6143a32353e04488c26d834ae5671855162ce2180d7
Tx public key: b7e84a7cf2a499ad3b978a673fb39711c00d5c9e92af9d2a516109d9a9a8e330
Timestamp: 1699390854 Timestamp [UCT]: 2023-11-07 21:00:54 Age [y:d:h:m:s]: 02:007:07:01:46
Block: 886695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 525000 RingCT/type: yes/0
Extra: 01b7e84a7cf2a499ad3b978a673fb39711c00d5c9e92af9d2a516109d9a9a8e3300211000000044b8f5122000000000000000000

1 output(s) for total of 0.707964341000 dcy

stealth address amount amount idx
00: 03df7edb21e8df83d16fa7c62f9d6ba6dab712f5b3d0cb2f7e2cc3e34b287f26 0.707964341000 1342530 of 0

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": 886705, "vin": [ { "gen": { "height": 886695 } } ], "vout": [ { "amount": 707964341, "target": { "key": "03df7edb21e8df83d16fa7c62f9d6ba6dab712f5b3d0cb2f7e2cc3e34b287f26" } } ], "extra": [ 1, 183, 232, 74, 124, 242, 164, 153, 173, 59, 151, 138, 103, 63, 179, 151, 17, 192, 13, 92, 158, 146, 175, 157, 42, 81, 97, 9, 217, 169, 168, 227, 48, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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