Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b67ef5ee583985a40340a18e91e5b29c37328014b08e19f58cd4f3a65ec2f54

Tx prefix hash: 6602191310e70efb1d865a8c0497343ad9060b0c3d59e7c7b6f096fe4535fbe4
Tx public key: d6c3215cf65ea8bd538e8269aa672979c2b356d0e4ffd12adf13da880fb984b4
Timestamp: 1746401969 Timestamp [UCT]: 2025-05-04 23:39:29 Age [y:d:h:m:s]: 00:200:23:45:42
Block: 1275917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141358 RingCT/type: yes/0
Extra: 01d6c3215cf65ea8bd538e8269aa672979c2b356d0e4ffd12adf13da880fb984b40211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5f6366c7337d158638e0e437a7dd480d7243d0bdc5a866a2d531a902dc7c27 0.600000000000 1763232 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": 1275927, "vin": [ { "gen": { "height": 1275917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5f6366c7337d158638e0e437a7dd480d7243d0bdc5a866a2d531a902dc7c27" } } ], "extra": [ 1, 214, 195, 33, 92, 246, 94, 168, 189, 83, 142, 130, 105, 170, 103, 41, 121, 194, 179, 86, 208, 228, 255, 209, 42, 223, 19, 218, 136, 15, 185, 132, 180, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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