Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b51672150d26bf0ee3da3f429d864b485407fe4e004481a723071073cef3b227

Tx prefix hash: 67f49558e707d15a269d2382d392f09afb914d8de3ebdb7b1d7dfdd602d79d9f
Tx public key: 0bae89696e406eaa3c9834f0cc84cfc7dd9454482f5d70e4299a1a0d97fb7e6a
Timestamp: 1722726034 Timestamp [UCT]: 2024-08-03 23:00:34 Age [y:d:h:m:s]: 00:173:09:44:14
Block: 1080153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124018 RingCT/type: yes/0
Extra: 010bae89696e406eaa3c9834f0cc84cfc7dd9454482f5d70e4299a1a0d97fb7e6a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f58586563b88fffc1dc01cead876faa9631b9b90f47abe2cfa16831bf63bfe0f 0.600000000000 1553406 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": 1080163, "vin": [ { "gen": { "height": 1080153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f58586563b88fffc1dc01cead876faa9631b9b90f47abe2cfa16831bf63bfe0f" } } ], "extra": [ 1, 11, 174, 137, 105, 110, 64, 110, 170, 60, 152, 52, 240, 204, 132, 207, 199, 221, 148, 84, 72, 47, 93, 112, 228, 41, 154, 26, 13, 151, 251, 126, 106, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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