Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c24dc189f49c33b53e11f7110d23e6619f0ec40d3ca6e2c915f4be3ae3129a98

Tx prefix hash: e4469f51ea19db26de2936484b03a91f46ab6e6b9c8402f9fd8a80cfdfad121a
Tx public key: dd682f5c97d13596c4eb87466b2710008528f0623633e3a9b221d27235992d77
Timestamp: 1726977531 Timestamp [UCT]: 2024-09-22 03:58:51 Age [y:d:h:m:s]: 00:063:13:28:58
Block: 1115402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45428 RingCT/type: yes/0
Extra: 01dd682f5c97d13596c4eb87466b2710008528f0623633e3a9b221d27235992d7702110000000391e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 1c889fb04fd5c3bf73db12b85d07067d3a8fef0369eaa143eb6e8ce937e757fd 0.608000000000 1595521 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": 1115412, "vin": [ { "gen": { "height": 1115402 } } ], "vout": [ { "amount": 608000000, "target": { "key": "1c889fb04fd5c3bf73db12b85d07067d3a8fef0369eaa143eb6e8ce937e757fd" } } ], "extra": [ 1, 221, 104, 47, 92, 151, 209, 53, 150, 196, 235, 135, 70, 107, 39, 16, 0, 133, 40, 240, 98, 54, 51, 227, 169, 178, 33, 210, 114, 53, 153, 45, 119, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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