Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1012f676c7caa3b4e126e7ef33ac3e8408c5ade9e79ac378d316c50d5cd2d179

Tx prefix hash: 6eb7f190557c88c8372fad76c7d7bf13c88d743738b240effa5a608a8c501e8e
Tx public key: 13d84dba1e03ad9738a57ee07cdf1c6a45fb7fbac648ec9ab414a810c3aaf05c
Timestamp: 1720388561 Timestamp [UCT]: 2024-07-07 21:42:41 Age [y:d:h:m:s]: 00:276:06:45:08
Block: 1060780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197396 RingCT/type: yes/0
Extra: 0113d84dba1e03ad9738a57ee07cdf1c6a45fb7fbac648ec9ab414a810c3aaf05c02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3558947133e91b43eb7be54f8f681d0af1031f1db18848ffb686c7c7f7026e 0.600000000000 1531265 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": 1060790, "vin": [ { "gen": { "height": 1060780 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3558947133e91b43eb7be54f8f681d0af1031f1db18848ffb686c7c7f7026e" } } ], "extra": [ 1, 19, 216, 77, 186, 30, 3, 173, 151, 56, 165, 126, 224, 124, 223, 28, 106, 69, 251, 127, 186, 198, 72, 236, 154, 180, 20, 168, 16, 195, 170, 240, 92, 2, 17, 0, 0, 0, 10, 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