Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48120ec1286bd1646e353f3e08620413e34e2a1e7c99ff9034e8df3d1e9a0aad

Tx prefix hash: 87d2299031040f47939ff8309817b19a79f4c5d87c2b7ff20242d98dc6fa8257
Tx public key: 09ebe1c7c7cf4ffb0a7ba663940fbb3db0ba36289b12786435b582c5d0ee7ee8
Timestamp: 1710610644 Timestamp [UCT]: 2024-03-16 17:37:24 Age [y:d:h:m:s]: 01:008:05:11:12
Block: 979732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266828 RingCT/type: yes/0
Extra: 0109ebe1c7c7cf4ffb0a7ba663940fbb3db0ba36289b12786435b582c5d0ee7ee80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae66a75add3dfe8d5276ada84a4c0104f86bd46865981aa9e35b66786090e8d8 0.600000000000 1439783 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": 979742, "vin": [ { "gen": { "height": 979732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae66a75add3dfe8d5276ada84a4c0104f86bd46865981aa9e35b66786090e8d8" } } ], "extra": [ 1, 9, 235, 225, 199, 199, 207, 79, 251, 10, 123, 166, 99, 148, 15, 187, 61, 176, 186, 54, 40, 155, 18, 120, 100, 53, 181, 130, 197, 208, 238, 126, 232, 2, 17, 0, 0, 0, 1, 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