Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93413eb58ebef3ee14207718b1860441204c07b641a2e92334c56ce6b2c412aa

Tx prefix hash: 073e386b31d195771b44da9b14147e69e3c6f1a4b278dea8571ab89754473c2b
Tx public key: c287a8fef8d62586b7d8d69d94473897580a3afb8fa6cb071e8ecc8c98735e39
Timestamp: 1731247780 Timestamp [UCT]: 2024-11-10 14:09:40 Age [y:d:h:m:s]: 00:128:20:37:07
Block: 1150723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91932 RingCT/type: yes/0
Extra: 01c287a8fef8d62586b7d8d69d94473897580a3afb8fa6cb071e8ecc8c98735e390211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d90c73a1bc107bbcc1e0d932daa265de8654647bc38bd916e47e541ab6621b7 0.600000000000 1636104 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": 1150733, "vin": [ { "gen": { "height": 1150723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d90c73a1bc107bbcc1e0d932daa265de8654647bc38bd916e47e541ab6621b7" } } ], "extra": [ 1, 194, 135, 168, 254, 248, 214, 37, 134, 183, 216, 214, 157, 148, 71, 56, 151, 88, 10, 58, 251, 143, 166, 203, 7, 30, 142, 204, 140, 152, 115, 94, 57, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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