Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d43e0518bf2d030b6d4e45c7d9196c8954cdca02a7dd07bde51da15e4958ba73

Tx prefix hash: 96b8bf3bbdb22da5eb8925eb025f9d4e33147b95bebd1f23f6b662674804aa15
Tx public key: b82cf83d9f31cdb4ec9efbf8993bfaed53f1bd58747998bf1a048e08cdc6d76c
Timestamp: 1724592123 Timestamp [UCT]: 2024-08-25 13:22:03 Age [y:d:h:m:s]: 00:290:13:30:08
Block: 1095620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207540 RingCT/type: yes/0
Extra: 01b82cf83d9f31cdb4ec9efbf8993bfaed53f1bd58747998bf1a048e08cdc6d76c02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cca77b6e48f2acb7b9c11041712ff82204b480e4b0c19b4e239af5b2f80c393d 0.600000000000 1570801 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": 1095630, "vin": [ { "gen": { "height": 1095620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cca77b6e48f2acb7b9c11041712ff82204b480e4b0c19b4e239af5b2f80c393d" } } ], "extra": [ 1, 184, 44, 248, 61, 159, 49, 205, 180, 236, 158, 251, 248, 153, 59, 250, 237, 83, 241, 189, 88, 116, 121, 152, 191, 26, 4, 142, 8, 205, 198, 215, 108, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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