Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4d3505003ca44cd088e558475f4964a41ae52e7fcf7fc080a5990969140eddb

Tx prefix hash: 35ef858c728002a33665ecf61306f0c32ea84e255192a925f539cfe99fbb026b
Tx public key: e87c94b570243dc71b24a2934d33dd55f4b18cda0733d1f24c8bcd304c1b1497
Timestamp: 1711271033 Timestamp [UCT]: 2024-03-24 09:03:53 Age [y:d:h:m:s]: 01:035:02:26:51
Block: 985213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286056 RingCT/type: yes/0
Extra: 01e87c94b570243dc71b24a2934d33dd55f4b18cda0733d1f24c8bcd304c1b149702110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a131b004436f0644543f6d78b5df4c3558b42376a6d39e3f1aa01cf669053fb 0.600000000000 1445422 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": 985223, "vin": [ { "gen": { "height": 985213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a131b004436f0644543f6d78b5df4c3558b42376a6d39e3f1aa01cf669053fb" } } ], "extra": [ 1, 232, 124, 148, 181, 112, 36, 61, 199, 27, 36, 162, 147, 77, 51, 221, 85, 244, 177, 140, 218, 7, 51, 209, 242, 76, 139, 205, 48, 76, 27, 20, 151, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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