Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1633bda2b86d95ab09465f2b61635bf9b989aaf0188165a49722ac75b7e85295

Tx prefix hash: db210c7633766e791c59d63e6ad5ebc2c4f48128a25fa48b35c984512b8f925b
Tx public key: c25011c7e47c0e495978d157ab089b3f156d3586a3ff2a614f1e63f7ec88e2ef
Timestamp: 1711926078 Timestamp [UCT]: 2024-03-31 23:01:18 Age [y:d:h:m:s]: 00:331:17:57:06
Block: 990633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237153 RingCT/type: yes/0
Extra: 01c25011c7e47c0e495978d157ab089b3f156d3586a3ff2a614f1e63f7ec88e2ef0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 187faa12e548f40d41d4c643f557fe1be90db2eb83400a61c5befe6fa691865c 0.600000000000 1450957 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": 990643, "vin": [ { "gen": { "height": 990633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "187faa12e548f40d41d4c643f557fe1be90db2eb83400a61c5befe6fa691865c" } } ], "extra": [ 1, 194, 80, 17, 199, 228, 124, 14, 73, 89, 120, 209, 87, 171, 8, 155, 63, 21, 109, 53, 134, 163, 255, 42, 97, 79, 30, 99, 247, 236, 136, 226, 239, 2, 17, 0, 0, 0, 3, 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