Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac994355df56c34b5dcae5702eeef635ab144e6a379f679cc095cb2302cd19ac

Tx prefix hash: bf68f38bf962a2741932f32b3f0461c9cc5dd2a91be3183a836709034a5d0e51
Tx public key: 13b20b8b7cd41933875d511343ef14923cd4d681435452e7d3c09f199028c8fc
Timestamp: 1733423870 Timestamp [UCT]: 2024-12-05 18:37:50 Age [y:d:h:m:s]: 00:133:15:42:10
Block: 1168744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95334 RingCT/type: yes/0
Extra: 0113b20b8b7cd41933875d511343ef14923cd4d681435452e7d3c09f199028c8fc0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7f0f404f3562b5071273a5f4c6c516d7c4a182a3e7ba8ee502c93b6e245c08a 0.600000000000 1654455 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": 1168754, "vin": [ { "gen": { "height": 1168744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7f0f404f3562b5071273a5f4c6c516d7c4a182a3e7ba8ee502c93b6e245c08a" } } ], "extra": [ 1, 19, 178, 11, 139, 124, 212, 25, 51, 135, 93, 81, 19, 67, 239, 20, 146, 60, 212, 214, 129, 67, 84, 82, 231, 211, 192, 159, 25, 144, 40, 200, 252, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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