Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6d66e00097a67967acd21c73895747c7b38179e3a2fd5ec26a3c081b0d64b7f

Tx prefix hash: 9490b4e5c31fdd8c56d965b3f966d327e707949ccca1a7316a7d8469b354ba42
Tx public key: 057d0475947d1826dafc66053e187759b56a60fa783fb68a97e1c5afc745dc94
Timestamp: 1721574969 Timestamp [UCT]: 2024-07-21 15:16:09 Age [y:d:h:m:s]: 01:108:19:47:22
Block: 1070607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336278 RingCT/type: yes/0
Extra: 01057d0475947d1826dafc66053e187759b56a60fa783fb68a97e1c5afc745dc9402110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f7bdd4fb67fb21e195b56c1abf2a20735446508106a45ab4d0b153006d98796 0.600000000000 1542512 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": 1070617, "vin": [ { "gen": { "height": 1070607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f7bdd4fb67fb21e195b56c1abf2a20735446508106a45ab4d0b153006d98796" } } ], "extra": [ 1, 5, 125, 4, 117, 148, 125, 24, 38, 218, 252, 102, 5, 62, 24, 119, 89, 181, 106, 96, 250, 120, 63, 182, 138, 151, 225, 197, 175, 199, 69, 220, 148, 2, 17, 0, 0, 0, 5, 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