Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49f945998c2dcd10ca82d6fb1117ab61f4e86d180a274744f081a92c1003d4fc

Tx prefix hash: 8ee17f4408487f6fa25c3bfdbe3412d4a658e0b75a14df01e0871948010c07df
Tx public key: d78fe67963b3b564cef1052c0d67b09a09b9eee88f50fd8771e872f2992310a8
Timestamp: 1713769445 Timestamp [UCT]: 2024-04-22 07:04:05 Age [y:d:h:m:s]: 01:169:21:30:55
Block: 1005895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380041 RingCT/type: yes/0
Extra: 01d78fe67963b3b564cef1052c0d67b09a09b9eee88f50fd8771e872f2992310a802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ac90ef72bc5783de594424bbfd619e8927f2ad6ef0fb0c7a7170cc003bbef33 0.600000000000 1466735 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": 1005905, "vin": [ { "gen": { "height": 1005895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ac90ef72bc5783de594424bbfd619e8927f2ad6ef0fb0c7a7170cc003bbef33" } } ], "extra": [ 1, 215, 143, 230, 121, 99, 179, 181, 100, 206, 241, 5, 44, 13, 103, 176, 154, 9, 185, 238, 232, 143, 80, 253, 135, 113, 232, 114, 242, 153, 35, 16, 168, 2, 17, 0, 0, 0, 4, 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