Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d304d9c6e4715f9b94f202108281c6df05177e6afac5768aa66174c659aa0b8d

Tx prefix hash: a0519b9449256045fb89b99fc3ebe592b515bf3d5eee8c594586b9167c62d0ef
Tx public key: a71aea82bc7baac7cc46f379d995f617ca70d83b2263b0bfb0c75db90554971b
Timestamp: 1735040049 Timestamp [UCT]: 2024-12-24 11:34:09 Age [y:d:h:m:s]: 00:089:15:24:06
Block: 1182131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63833 RingCT/type: yes/0
Extra: 01a71aea82bc7baac7cc46f379d995f617ca70d83b2263b0bfb0c75db90554971b0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a1d4da3afe826a60c41a58d9a426a2e7f2c45a972abb79010111e56eacda9b3 0.600000000000 1668564 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": 1182141, "vin": [ { "gen": { "height": 1182131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a1d4da3afe826a60c41a58d9a426a2e7f2c45a972abb79010111e56eacda9b3" } } ], "extra": [ 1, 167, 26, 234, 130, 188, 123, 170, 199, 204, 70, 243, 121, 217, 149, 246, 23, 202, 112, 216, 59, 34, 99, 176, 191, 176, 199, 93, 185, 5, 84, 151, 27, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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