Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf6acb0ab48863d68af3f8f5793e7b1573c7281396dce2755ed4fb3216cfb376

Tx prefix hash: 53fa70cb1cd3d80bbe859339f27d93b700a836418d925427808baed6c26a48c3
Tx public key: 3d666d5a06d1d8b854b084564c2da45bd9c21a6310e32aeb70693f3dd70a30a1
Timestamp: 1723150914 Timestamp [UCT]: 2024-08-08 21:01:54 Age [y:d:h:m:s]: 00:269:02:25:43
Block: 1083671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192239 RingCT/type: yes/0
Extra: 013d666d5a06d1d8b854b084564c2da45bd9c21a6310e32aeb70693f3dd70a30a1021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78eeb50aeb89c074742b039692d6c3f4b657ccc78316f25208cefbf18999e44c 0.600000000000 1557674 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": 1083681, "vin": [ { "gen": { "height": 1083671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78eeb50aeb89c074742b039692d6c3f4b657ccc78316f25208cefbf18999e44c" } } ], "extra": [ 1, 61, 102, 109, 90, 6, 209, 216, 184, 84, 176, 132, 86, 76, 45, 164, 91, 217, 194, 26, 99, 16, 227, 42, 235, 112, 105, 63, 61, 215, 10, 48, 161, 2, 17, 0, 0, 0, 4, 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