Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5629c29d327f932d42bbb7bd0f8ebc2c0c5ddfbac9920f7972997cf11eecb9bc

Tx prefix hash: 0ed68b3396cd335d5e531b67176d4b4470d306932ee97ba25afe8bf48b17d291
Tx public key: 63897e6d57e3a1d3504f51293372091cf93b634cf8ae962cf0ef19ec90c84a53
Timestamp: 1724327707 Timestamp [UCT]: 2024-08-22 11:55:07 Age [y:d:h:m:s]: 00:227:18:12:51
Block: 1093451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162616 RingCT/type: yes/0
Extra: 0163897e6d57e3a1d3504f51293372091cf93b634cf8ae962cf0ef19ec90c84a5302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e0f43f29dcf0a681c6fd0edb0cafcbf43d59f8949ee0dbe69f9adb6d1c849d 0.600000000000 1568398 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": 1093461, "vin": [ { "gen": { "height": 1093451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e0f43f29dcf0a681c6fd0edb0cafcbf43d59f8949ee0dbe69f9adb6d1c849d" } } ], "extra": [ 1, 99, 137, 126, 109, 87, 227, 161, 211, 80, 79, 81, 41, 51, 114, 9, 28, 249, 59, 99, 76, 248, 174, 150, 44, 240, 239, 25, 236, 144, 200, 74, 83, 2, 17, 0, 0, 0, 4, 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