Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7ad43ae5aa2a7c993de759d7d9ad19f368248c4bd2c61fbfde42c5ad51d58f2

Tx prefix hash: d3793919f0f9a944017a569a7a9622386482ab3c74b934704836b233c808978e
Tx public key: f3b4d29e18a57aa72c9361a217ed1301d28796e01b5132abaa7fd2b93148e9b5
Timestamp: 1717008737 Timestamp [UCT]: 2024-05-29 18:52:17 Age [y:d:h:m:s]: 00:333:08:33:44
Block: 1032757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238271 RingCT/type: yes/0
Extra: 01f3b4d29e18a57aa72c9361a217ed1301d28796e01b5132abaa7fd2b93148e9b50211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e1ec4f56ab5e9352aa88d01e63b42b8e7c1658a10f0f6d5f0cd630014fb4742 0.600000000000 1501212 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": 1032767, "vin": [ { "gen": { "height": 1032757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e1ec4f56ab5e9352aa88d01e63b42b8e7c1658a10f0f6d5f0cd630014fb4742" } } ], "extra": [ 1, 243, 180, 210, 158, 24, 165, 122, 167, 44, 147, 97, 162, 23, 237, 19, 1, 210, 135, 150, 224, 27, 81, 50, 171, 170, 127, 210, 185, 49, 72, 233, 181, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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