Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a262baa8860981f9d9d2606b8088c5a315d3e79971f188401f874d8117b7273b

Tx prefix hash: a15450bf8a3ed90b9dc33b824dbbe61ee2fe804a5d2bac520d481ab8d02c1eba
Tx public key: 2f5c581d7598bda38c49942d90be76bcfac8cfc508dc863ff2f6de571722d50b
Timestamp: 1705347532 Timestamp [UCT]: 2024-01-15 19:38:52 Age [y:d:h:m:s]: 01:083:12:03:46
Block: 936059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320774 RingCT/type: yes/0
Extra: 012f5c581d7598bda38c49942d90be76bcfac8cfc508dc863ff2f6de571722d50b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5f7d28886028ef833db7ce72ed611be3a275201abec81dcb50aba340f3a3cc2 0.600000000000 1394081 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": 936069, "vin": [ { "gen": { "height": 936059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5f7d28886028ef833db7ce72ed611be3a275201abec81dcb50aba340f3a3cc2" } } ], "extra": [ 1, 47, 92, 88, 29, 117, 152, 189, 163, 140, 73, 148, 45, 144, 190, 118, 188, 250, 200, 207, 197, 8, 220, 134, 63, 242, 246, 222, 87, 23, 34, 213, 11, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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