Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f72edec511ae028cfbd2700f6981d2ca1c2faaf67789cf6ac06fc7b6a397e157

Tx prefix hash: 02980751acc91253c2f300acf8d1e08db84fce71d981b0d2d8a09bb72f46e266
Tx public key: 044b8fc5956160b3dfd89312f07d81295301f739ff68c774f68ae16aa695b9c3
Timestamp: 1722234032 Timestamp [UCT]: 2024-07-29 06:20:32 Age [y:d:h:m:s]: 00:242:02:30:21
Block: 1076079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172927 RingCT/type: yes/0
Extra: 01044b8fc5956160b3dfd89312f07d81295301f739ff68c774f68ae16aa695b9c302110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d98300937c2270ce577227caf6d32f71e994743638aa660a9d0fc1c1439e79ad 0.600000000000 1548614 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": 1076089, "vin": [ { "gen": { "height": 1076079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d98300937c2270ce577227caf6d32f71e994743638aa660a9d0fc1c1439e79ad" } } ], "extra": [ 1, 4, 75, 143, 197, 149, 97, 96, 179, 223, 216, 147, 18, 240, 125, 129, 41, 83, 1, 247, 57, 255, 104, 199, 116, 246, 138, 225, 106, 166, 149, 185, 195, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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