Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a515a04eda58dc6b74023acbaa09241bfc24532ca8ecdeb1a712c8584c37e2a

Tx prefix hash: 81ea6d694f7b5500300f579c1e744142af83e7d02d0f77dfe80ed965f4a1f6f6
Tx public key: db6b716aa691431a15d805a7e509af824d3687ab4ba3916e8d73f6c29f251b79
Timestamp: 1583235181 Timestamp [UCT]: 2020-03-03 11:33:01 Age [y:d:h:m:s]: 04:297:13:48:44
Block: 75329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1107216 RingCT/type: yes/0
Extra: 01db6b716aa691431a15d805a7e509af824d3687ab4ba3916e8d73f6c29f251b790211000001887adf42d3000000000000000000

1 output(s) for total of 345.465393637000 dcy

stealth address amount amount idx
00: bfabd12d69adccf0ff722095619ea4a61856e6936b7fd7e54f1856aaddbd729b 345.465393637000 139256 of 0

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": 75339, "vin": [ { "gen": { "height": 75329 } } ], "vout": [ { "amount": 345465393637, "target": { "key": "bfabd12d69adccf0ff722095619ea4a61856e6936b7fd7e54f1856aaddbd729b" } } ], "extra": [ 1, 219, 107, 113, 106, 166, 145, 67, 26, 21, 216, 5, 167, 229, 9, 175, 130, 77, 54, 135, 171, 75, 163, 145, 110, 141, 115, 246, 194, 159, 37, 27, 121, 2, 17, 0, 0, 1, 136, 122, 223, 66, 211, 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