Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0a960416653dc01c1d2bcafb4fe1559c6652c2d0327b29bc83c1ebbf971c2e9

Tx prefix hash: fc384d317be1b60888a1ee7133dbcc6786e3dcd7a4b2cc486ae6067259796510
Tx public key: 78311cad0a401cae8243d61042d28685fcd546c9a5b258e789707dd82aa2567a
Timestamp: 1656978614 Timestamp [UCT]: 2022-07-04 23:50:14 Age [y:d:h:m:s]: 02:259:03:24:27
Block: 536768 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706371 RingCT/type: yes/0
Extra: 0178311cad0a401cae8243d61042d28685fcd546c9a5b258e789707dd82aa2567a0211000000014da16a3a000000000000000000

1 output(s) for total of 10.220330609000 dcy

stealth address amount amount idx
00: a0ce5dca6758d4a1103bd01257fc9573f7d8c2850c2ac36a4522c1c458e21fdd 10.220330609000 966569 of 0

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": 536778, "vin": [ { "gen": { "height": 536768 } } ], "vout": [ { "amount": 10220330609, "target": { "key": "a0ce5dca6758d4a1103bd01257fc9573f7d8c2850c2ac36a4522c1c458e21fdd" } } ], "extra": [ 1, 120, 49, 28, 173, 10, 64, 28, 174, 130, 67, 214, 16, 66, 210, 134, 133, 252, 213, 70, 201, 165, 178, 88, 231, 137, 112, 125, 216, 42, 162, 86, 122, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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