Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3953f6eaa5d9239558cff3e4036ec62aa73f81b9895d0ede0a993f5fff2b81c8

Tx prefix hash: 72aabb3fd40b1d28c75e2633542ab8a739fe7ad4f6f458af67d92df8f1940837
Tx public key: 92a0f7f7d1e388c1015bb0538c0ad3b03844ad09db111ea5641ddfa6818f9514
Timestamp: 1708999839 Timestamp [UCT]: 2024-02-27 02:10:39 Age [y:d:h:m:s]: 01:080:01:54:22
Block: 966371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318263 RingCT/type: yes/0
Extra: 0192a0f7f7d1e388c1015bb0538c0ad3b03844ad09db111ea5641ddfa6818f95140211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c20aced60e05c28fd8e81e40d95d7a19ab63ad423cdb69d1f63c380a23cc938b 0.600000000000 1426128 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": 966381, "vin": [ { "gen": { "height": 966371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c20aced60e05c28fd8e81e40d95d7a19ab63ad423cdb69d1f63c380a23cc938b" } } ], "extra": [ 1, 146, 160, 247, 247, 209, 227, 136, 193, 1, 91, 176, 83, 140, 10, 211, 176, 56, 68, 173, 9, 219, 17, 30, 165, 100, 29, 223, 166, 129, 143, 149, 20, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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