Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5122c9ddfdb1f84ee2d71f6fb41df20cb52da9b34b9a06c919de12372e01d85

Tx prefix hash: 04a7c2ad391177b660e2296e375aba6ea0ee81ad75ecbd01ed0c2a169c49d1a1
Tx public key: c26578f7e9be28cd52a2edb81363b0ddb1f1e02bc4767d51d7511898bf49928c
Timestamp: 1715100355 Timestamp [UCT]: 2024-05-07 16:45:55 Age [y:d:h:m:s]: 01:008:17:11:54
Block: 1016934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267156 RingCT/type: yes/0
Extra: 01c26578f7e9be28cd52a2edb81363b0ddb1f1e02bc4767d51d7511898bf49928c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fe44b9ccbad3c88e677d28b02f640aee283e7c652f6131cab261e6a304dcca2 0.600000000000 1480663 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": 1016944, "vin": [ { "gen": { "height": 1016934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fe44b9ccbad3c88e677d28b02f640aee283e7c652f6131cab261e6a304dcca2" } } ], "extra": [ 1, 194, 101, 120, 247, 233, 190, 40, 205, 82, 162, 237, 184, 19, 99, 176, 221, 177, 241, 224, 43, 196, 118, 125, 81, 215, 81, 24, 152, 191, 73, 146, 140, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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