Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471bfae7144a64606da276ac895864296c7129e85c08b8e861f6b1656b0e973c

Tx prefix hash: 97777bba593d302ea0f0e0a13a5b5fa2bc55a3c20f881cd909470bf32276dbd3
Tx public key: a4204796f8d42cf04f5d5eba706663d630ba4994fd57c80342dc7a3f706a7c89
Timestamp: 1729109167 Timestamp [UCT]: 2024-10-16 20:06:07 Age [y:d:h:m:s]: 00:227:17:33:34
Block: 1133075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162586 RingCT/type: yes/0
Extra: 01a4204796f8d42cf04f5d5eba706663d630ba4994fd57c80342dc7a3f706a7c89021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6de4898ad47dc49671eab3a161d089a2f0dc81a3630c6fe1eb81db266c82c83d 0.600000000000 1616144 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": 1133085, "vin": [ { "gen": { "height": 1133075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6de4898ad47dc49671eab3a161d089a2f0dc81a3630c6fe1eb81db266c82c83d" } } ], "extra": [ 1, 164, 32, 71, 150, 248, 212, 44, 240, 79, 93, 94, 186, 112, 102, 99, 214, 48, 186, 73, 148, 253, 87, 200, 3, 66, 220, 122, 63, 112, 106, 124, 137, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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