Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a35fa64064371d9b6a444383b394f56ddbf2b480b0dae4894078e3f3c09465

Tx prefix hash: b9fa67a2b3e7c8ee501bd9ef2b5613e06d6c037258a3cfe2d3de55a4da6d2e97
Tx public key: f2d3efe83e6e575a9ca50b3a75714513a0584f043e21d12fcff810e1879d6b6f
Timestamp: 1713464634 Timestamp [UCT]: 2024-04-18 18:23:54 Age [y:d:h:m:s]: 01:047:15:45:56
Block: 1003358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295063 RingCT/type: yes/0
Extra: 01f2d3efe83e6e575a9ca50b3a75714513a0584f043e21d12fcff810e1879d6b6f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e587b3b53415514c240590e09f2ace24024875b8ba0e4d3b55cbf1e964caa04 0.600000000000 1463888 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": 1003368, "vin": [ { "gen": { "height": 1003358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e587b3b53415514c240590e09f2ace24024875b8ba0e4d3b55cbf1e964caa04" } } ], "extra": [ 1, 242, 211, 239, 232, 62, 110, 87, 90, 156, 165, 11, 58, 117, 113, 69, 19, 160, 88, 79, 4, 62, 33, 209, 47, 207, 248, 16, 225, 135, 157, 107, 111, 2, 17, 0, 0, 0, 2, 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