Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 939dd3a31bd5240db3a7590841904049bb29aff63ec3d31ad862f16592a9f787

Tx prefix hash: c52ed968a7cd3eb342ea63b7d49284bfcedbbb2db2c18162f1d22d4aa7c5f464
Tx public key: 9dda35faf8c5fe568156da505e0ce4a4be861e3b5f73733fa274a359e8ffd525
Timestamp: 1735210708 Timestamp [UCT]: 2024-12-26 10:58:28 Age [y:d:h:m:s]: 00:095:18:38:06
Block: 1183543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68225 RingCT/type: yes/0
Extra: 019dda35faf8c5fe568156da505e0ce4a4be861e3b5f73733fa274a359e8ffd525021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b6f9b60f64414f54b449e5c1e0f2668c05622de5a7b4218132542283b8153c3 0.600000000000 1669988 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": 1183553, "vin": [ { "gen": { "height": 1183543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b6f9b60f64414f54b449e5c1e0f2668c05622de5a7b4218132542283b8153c3" } } ], "extra": [ 1, 157, 218, 53, 250, 248, 197, 254, 86, 129, 86, 218, 80, 94, 12, 228, 164, 190, 134, 30, 59, 95, 115, 115, 63, 162, 116, 163, 89, 232, 255, 213, 37, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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