Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f1d1b85418ac01bb6ae2d5671e46e788a5332a1a4a1f16423d8152db756e3a3

Tx prefix hash: b39e2f9aaa4fc4d9bd31b36f1a3048addd3d7d90a421039ab1a9f335ab838e2a
Tx public key: 63ff3df6e87a4906064a91c6161a1d4110e68c1e4b3f1b9fb0ec806206c63cee
Timestamp: 1727974739 Timestamp [UCT]: 2024-10-03 16:58:59 Age [y:d:h:m:s]: 00:183:07:25:38
Block: 1123675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130803 RingCT/type: yes/0
Extra: 0163ff3df6e87a4906064a91c6161a1d4110e68c1e4b3f1b9fb0ec806206c63cee02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cbe82a1beb6ba1eadadf07ab07c5929cc105ba78da12cd38151a2d647348c0e 0.600000000000 1606210 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": 1123685, "vin": [ { "gen": { "height": 1123675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cbe82a1beb6ba1eadadf07ab07c5929cc105ba78da12cd38151a2d647348c0e" } } ], "extra": [ 1, 99, 255, 61, 246, 232, 122, 73, 6, 6, 74, 145, 198, 22, 26, 29, 65, 16, 230, 140, 30, 75, 63, 27, 159, 176, 236, 128, 98, 6, 198, 60, 238, 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