Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95ddece25c30c12645e20edaf5e63a9df52f105fd6dfe7d56487d25bc61bd3cc

Tx prefix hash: df00c5b8b2289d1697cc5f54b0c1dc64c1e34a3b90a208d7b5427811fec5221f
Tx public key: 59822eeb442a23f6e554edcd6f7d2ab873f993a8735a2845095f77b16812c259
Timestamp: 1716597323 Timestamp [UCT]: 2024-05-25 00:35:23 Age [y:d:h:m:s]: 00:302:13:00:54
Block: 1029355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216232 RingCT/type: yes/0
Extra: 0159822eeb442a23f6e554edcd6f7d2ab873f993a8735a2845095f77b16812c2590211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e1b3353c5d5f15f6e8693c56831b286bd170f8ef0e83588afb6b844505b4dc 0.600000000000 1497422 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": 1029365, "vin": [ { "gen": { "height": 1029355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e1b3353c5d5f15f6e8693c56831b286bd170f8ef0e83588afb6b844505b4dc" } } ], "extra": [ 1, 89, 130, 46, 235, 68, 42, 35, 246, 229, 84, 237, 205, 111, 125, 42, 184, 115, 249, 147, 168, 115, 90, 40, 69, 9, 95, 119, 177, 104, 18, 194, 89, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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