Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26e61ed5afd5e3a0af2c4e2859c5f17dc88dbafc2e522aa4db7f170b00320234

Tx prefix hash: eb8b12f21cd912954af6b433627a92b2d217dd3382b2feaa26b525ef09fdffb4
Tx public key: b031f32d8cf883976ec550d9ce3051971946b93afcde2081928fab8d92e531e7
Timestamp: 1714889600 Timestamp [UCT]: 2024-05-05 06:13:20 Age [y:d:h:m:s]: 00:329:19:23:16
Block: 1015202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235728 RingCT/type: yes/0
Extra: 01b031f32d8cf883976ec550d9ce3051971946b93afcde2081928fab8d92e531e702110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e29d424b36ce3de608a859df7bd3efa5fdf3e9fbf4ad0119fc0a13735efa1d9 0.600000000000 1478497 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": 1015212, "vin": [ { "gen": { "height": 1015202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e29d424b36ce3de608a859df7bd3efa5fdf3e9fbf4ad0119fc0a13735efa1d9" } } ], "extra": [ 1, 176, 49, 243, 45, 140, 248, 131, 151, 110, 197, 80, 217, 206, 48, 81, 151, 25, 70, 185, 58, 252, 222, 32, 129, 146, 143, 171, 141, 146, 229, 49, 231, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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