Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad502f1efb33d4d7e90dc9c81ac282f5172a3dd92bc3c9ed0c271f1311363812

Tx prefix hash: e54105e619ac3e34d9a8a970b3d82938d536362d8617ee2cbf96c853be5246b0
Tx public key: f3ad43cbe881fb3dc5de646cda3c9aa6d286bb8a4d9c124fdaa3be2ffd5961e8
Timestamp: 1714979283 Timestamp [UCT]: 2024-05-06 07:08:03 Age [y:d:h:m:s]: 00:138:15:40:05
Block: 1015935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99315 RingCT/type: yes/0
Extra: 01f3ad43cbe881fb3dc5de646cda3c9aa6d286bb8a4d9c124fdaa3be2ffd5961e802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 961993d1b42d1a203905040f174ea94a1438c4316e5f96a7817cfc125171360a 0.600000000000 1479378 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": 1015945, "vin": [ { "gen": { "height": 1015935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "961993d1b42d1a203905040f174ea94a1438c4316e5f96a7817cfc125171360a" } } ], "extra": [ 1, 243, 173, 67, 203, 232, 129, 251, 61, 197, 222, 100, 108, 218, 60, 154, 166, 210, 134, 187, 138, 77, 156, 18, 79, 218, 163, 190, 47, 253, 89, 97, 232, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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