Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e39a3acf4e926d2b5b66d9abe802d342fbfcc50a6b6e37a60a3d43be4c18511b

Tx prefix hash: 1b2ca63bef8920237a543b514cbc0c58aad59939e1f8a3787bdd18cc89a27b5e
Tx public key: ccd88ba95d93833d0e8901058311c869ed87f365ea28736bac738febd196e40e
Timestamp: 1708124733 Timestamp [UCT]: 2024-02-16 23:05:33 Age [y:d:h:m:s]: 01:038:13:02:10
Block: 959095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288569 RingCT/type: yes/0
Extra: 01ccd88ba95d93833d0e8901058311c869ed87f365ea28736bac738febd196e40e02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2c9b1de8c5e4682823b270c8b4b704c3382ba7d4c449c7eb69b44df3a8aa651 0.600000000000 1418624 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": 959105, "vin": [ { "gen": { "height": 959095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2c9b1de8c5e4682823b270c8b4b704c3382ba7d4c449c7eb69b44df3a8aa651" } } ], "extra": [ 1, 204, 216, 139, 169, 93, 147, 131, 61, 14, 137, 1, 5, 131, 17, 200, 105, 237, 135, 243, 101, 234, 40, 115, 107, 172, 115, 143, 235, 209, 150, 228, 14, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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