Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5346be57f5349b5ecdc6090e543608630629d21f524eb04948fa783bd03124ad

Tx prefix hash: 2192c0fb8bd6adeaa28f5a51bcaee2aed7e91624c7907b16a026cca766747def
Tx public key: f76f9871a6e5e608ec1ae5fe26ed01d9e811aa47d6f798a3508330019b9f8d3a
Timestamp: 1723142358 Timestamp [UCT]: 2024-08-08 18:39:18 Age [y:d:h:m:s]: 00:292:21:47:03
Block: 1083598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209283 RingCT/type: yes/0
Extra: 01f76f9871a6e5e608ec1ae5fe26ed01d9e811aa47d6f798a3508330019b9f8d3a02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c958f73b39324bc361c2e0a0702aa584ec73f47afa0c29c67e55f2cbc7695256 0.600000000000 1557579 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": 1083608, "vin": [ { "gen": { "height": 1083598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c958f73b39324bc361c2e0a0702aa584ec73f47afa0c29c67e55f2cbc7695256" } } ], "extra": [ 1, 247, 111, 152, 113, 166, 229, 230, 8, 236, 26, 229, 254, 38, 237, 1, 217, 232, 17, 170, 71, 214, 247, 152, 163, 80, 131, 48, 1, 155, 159, 141, 58, 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