Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 944eae462a1a0b9e4afe0e705d36cb25bbdbcfa86ab963d65971c3a75e826e33

Tx prefix hash: fdca499015124ee082262ece46b41a4ed029dda38ce5d06f433a3af66f54ce72
Tx public key: 29f914f870bc3d7118702f6b69b4d7a30388c84cdb13b8057531cc7ce8dd451c
Timestamp: 1718885616 Timestamp [UCT]: 2024-06-20 12:13:36 Age [y:d:h:m:s]: 00:346:10:49:09
Block: 1048324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247615 RingCT/type: yes/0
Extra: 0129f914f870bc3d7118702f6b69b4d7a30388c84cdb13b8057531cc7ce8dd451c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1d2d5414d21f768eaf6f6da99884e2a93eada0d4f2809a44a972a9d86be09db 0.600000000000 1518381 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": 1048334, "vin": [ { "gen": { "height": 1048324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1d2d5414d21f768eaf6f6da99884e2a93eada0d4f2809a44a972a9d86be09db" } } ], "extra": [ 1, 41, 249, 20, 248, 112, 188, 61, 113, 24, 112, 47, 107, 105, 180, 215, 163, 3, 136, 200, 76, 219, 19, 184, 5, 117, 49, 204, 124, 232, 221, 69, 28, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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