Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c799e1779a9fe17929b47f5d2bef189bb07bfa98a3666be1ff6c4d7f88b3f872

Tx prefix hash: c5529e7e69794082be40e5cab94cfd233d51c56cb6dc37d49a9749ca68ad314a
Tx public key: 28a0b62cf8da4aec1cb564be1e6e55b97e0c0608298031ddff5646f68b3a3288
Timestamp: 1733953084 Timestamp [UCT]: 2024-12-11 21:38:04 Age [y:d:h:m:s]: 00:187:14:48:53
Block: 1173141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133813 RingCT/type: yes/0
Extra: 0128a0b62cf8da4aec1cb564be1e6e55b97e0c0608298031ddff5646f68b3a3288021100000002c7ca14c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e2ebed86f8ba645843218449e43b130db6a46bb428e82b302971246d1c3830c 0.600000000000 1659128 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": 1173151, "vin": [ { "gen": { "height": 1173141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e2ebed86f8ba645843218449e43b130db6a46bb428e82b302971246d1c3830c" } } ], "extra": [ 1, 40, 160, 182, 44, 248, 218, 74, 236, 28, 181, 100, 190, 30, 110, 85, 185, 126, 12, 6, 8, 41, 128, 49, 221, 255, 86, 70, 246, 139, 58, 50, 136, 2, 17, 0, 0, 0, 2, 199, 202, 20, 193, 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