Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747d0a7c7a99836c263ea2b43c963c5b6a797e3aa292d21ffe78425e7a8c0cfe

Tx prefix hash: 7bb781347661ce216cfa64401a54edc1db43a4e2157fd2954c7c6e0a0b830842
Tx public key: cdf63f3652ed65a435a74b79142073fee884a4c4a514e8b344440fe5d7be7351
Timestamp: 1727174597 Timestamp [UCT]: 2024-09-24 10:43:17 Age [y:d:h:m:s]: 00:230:11:19:45
Block: 1117039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164550 RingCT/type: yes/0
Extra: 01cdf63f3652ed65a435a74b79142073fee884a4c4a514e8b344440fe5d7be735102110000001791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6cebfd52191eb9a42563ac1b99690b1c65ebac0784a11134cc5a2c72fc89826a 0.600000000000 1597730 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": 1117049, "vin": [ { "gen": { "height": 1117039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6cebfd52191eb9a42563ac1b99690b1c65ebac0784a11134cc5a2c72fc89826a" } } ], "extra": [ 1, 205, 246, 63, 54, 82, 237, 101, 164, 53, 167, 75, 121, 20, 32, 115, 254, 232, 132, 164, 196, 165, 20, 232, 179, 68, 68, 15, 229, 215, 190, 115, 81, 2, 17, 0, 0, 0, 23, 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