Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c99d09dea1ba58b0a83ced37e56b4a6dc0b767d4b0c52bfe215ecece450d394

Tx prefix hash: d4b25e2f1de4a9242dcbedb620d94f20ffaa4d272f3c205e2568b1d83c89693c
Tx public key: dae9596e77188ed408f93e9fc9e6d26aec9289216bf88600c875521db7366588
Timestamp: 1733158477 Timestamp [UCT]: 2024-12-02 16:54:37 Age [y:d:h:m:s]: 00:121:09:46:02
Block: 1166545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86562 RingCT/type: yes/0
Extra: 01dae9596e77188ed408f93e9fc9e6d26aec9289216bf88600c875521db73665880211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f268441b16eeefb5782a93351a1d0a0297db307a96f91f7bd0d7bdcef1e03d 0.600000000000 1652232 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": 1166555, "vin": [ { "gen": { "height": 1166545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f268441b16eeefb5782a93351a1d0a0297db307a96f91f7bd0d7bdcef1e03d" } } ], "extra": [ 1, 218, 233, 89, 110, 119, 24, 142, 212, 8, 249, 62, 159, 201, 230, 210, 106, 236, 146, 137, 33, 107, 248, 134, 0, 200, 117, 82, 29, 183, 54, 101, 136, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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