Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa0bf0ab29127f34ad0a7fb45911206fb9ff865ed35609ac8046ec9fee8c270b

Tx prefix hash: 82a892b41b0e1aca7c185403bd88ce5591644c74d593d61be0e2bafe68139098
Tx public key: a2550f2b044d2ff3b3090fd9d4f9c0473a24c2d0576b9b72779c134ce816b61a
Timestamp: 1736541696 Timestamp [UCT]: 2025-01-10 20:41:36 Age [y:d:h:m:s]: 00:068:10:13:02
Block: 1194555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48691 RingCT/type: yes/0
Extra: 01a2550f2b044d2ff3b3090fd9d4f9c0473a24c2d0576b9b72779c134ce816b61a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c238e894dc0b559f4e84492e0392538ff66beed6e1d09ad72a291238664c8cff 0.600000000000 1681130 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": 1194565, "vin": [ { "gen": { "height": 1194555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c238e894dc0b559f4e84492e0392538ff66beed6e1d09ad72a291238664c8cff" } } ], "extra": [ 1, 162, 85, 15, 43, 4, 77, 47, 243, 179, 9, 15, 217, 212, 249, 192, 71, 58, 36, 194, 208, 87, 107, 155, 114, 119, 156, 19, 76, 232, 22, 182, 26, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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