Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29bbf01055624e897a0306b93394803da7ca28d1401037cde838fef5bb5585dd

Tx prefix hash: bcd98244b88f52a958afc622afb3918079656d3b282ed3d0a8af5e7dfc3d5ea0
Tx public key: 3769c2b32d8e39a9d5ae48738718c1a2215ce76fdeebd2909a0ad0348aafc68b
Timestamp: 1725276838 Timestamp [UCT]: 2024-09-02 11:33:58 Age [y:d:h:m:s]: 00:127:19:01:15
Block: 1101300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91402 RingCT/type: yes/0
Extra: 013769c2b32d8e39a9d5ae48738718c1a2215ce76fdeebd2909a0ad0348aafc68b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b680617168b6c2e41513c94594304fb4ab0f0f3bf18b808e8ee69549a05f0dc 0.600000000000 1577297 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": 1101310, "vin": [ { "gen": { "height": 1101300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b680617168b6c2e41513c94594304fb4ab0f0f3bf18b808e8ee69549a05f0dc" } } ], "extra": [ 1, 55, 105, 194, 179, 45, 142, 57, 169, 213, 174, 72, 115, 135, 24, 193, 162, 33, 92, 231, 111, 222, 235, 210, 144, 154, 10, 208, 52, 138, 175, 198, 139, 2, 17, 0, 0, 0, 9, 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