Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e760261b6e7a332b891ad22753b5a648c898027b535a6c6b4d83564ae881fa92

Tx prefix hash: 20c65e3a082685b5e7537a513ed351b1ea879903935cbaa24847dce93162f390
Tx public key: e5c39c810a2461eb8342f0ce26c3212f95df16cf7873c44d1f2fef0bc1156086
Timestamp: 1705038814 Timestamp [UCT]: 2024-01-12 05:53:34 Age [y:d:h:m:s]: 01:089:21:47:21
Block: 933494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325377 RingCT/type: yes/0
Extra: 01e5c39c810a2461eb8342f0ce26c3212f95df16cf7873c44d1f2fef0bc115608602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42d8ae352263ff7d02d7418ae0dacc34ff8c23767a336faf8e490041e37e2483 0.600000000000 1391456 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": 933504, "vin": [ { "gen": { "height": 933494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42d8ae352263ff7d02d7418ae0dacc34ff8c23767a336faf8e490041e37e2483" } } ], "extra": [ 1, 229, 195, 156, 129, 10, 36, 97, 235, 131, 66, 240, 206, 38, 195, 33, 47, 149, 223, 22, 207, 120, 115, 196, 77, 31, 47, 239, 11, 193, 21, 96, 134, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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