Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6767982ebae3ca7d33315c3186f74e738bbdce1d59fd19fcf866fce1f42ac2e

Tx prefix hash: 1981fe6875437419e7f7a6f0d490c1c37c6f788d5080537c3cf44a4b7b7ecd37
Tx public key: 20256e86e7b2a6a52e83712b24cec6d2bcf9cc949cb77c2d182ed5bf82d0664d
Timestamp: 1728087521 Timestamp [UCT]: 2024-10-05 00:18:41 Age [y:d:h:m:s]: 00:202:05:37:19
Block: 1124601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144356 RingCT/type: yes/0
Extra: 0120256e86e7b2a6a52e83712b24cec6d2bcf9cc949cb77c2d182ed5bf82d0664d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e7265fceff7ce52eef8fbb818574c15a719109156c3353dbaef70da31b0e194 0.600000000000 1607250 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": 1124611, "vin": [ { "gen": { "height": 1124601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7265fceff7ce52eef8fbb818574c15a719109156c3353dbaef70da31b0e194" } } ], "extra": [ 1, 32, 37, 110, 134, 231, 178, 166, 165, 46, 131, 113, 43, 36, 206, 198, 210, 188, 249, 204, 148, 156, 183, 124, 45, 24, 46, 213, 191, 130, 208, 102, 77, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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