Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b82932fc35530fe53eb6875ad2da607c25256bc30d5d3a259d0bce3774ed37c7

Tx prefix hash: 6ca0a6ad66390ff7118e7c9ff883d4fb1b359685436cbf6a3ae2aa170a509e5a
Tx public key: 04095e25bade4f82d74e1a10abac8f3f115f0e049d18a947507644355d94f67b
Timestamp: 1727458449 Timestamp [UCT]: 2024-09-27 17:34:09 Age [y:d:h:m:s]: 00:057:17:27:38
Block: 1119390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41251 RingCT/type: yes/0
Extra: 0104095e25bade4f82d74e1a10abac8f3f115f0e049d18a947507644355d94f67b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdaa2702bd0eb57f02713fb65e8de2beda5933b9903a32b5f15eca2bcd60a184 0.600000000000 1600929 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": 1119400, "vin": [ { "gen": { "height": 1119390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdaa2702bd0eb57f02713fb65e8de2beda5933b9903a32b5f15eca2bcd60a184" } } ], "extra": [ 1, 4, 9, 94, 37, 186, 222, 79, 130, 215, 78, 26, 16, 171, 172, 143, 63, 17, 95, 14, 4, 157, 24, 169, 71, 80, 118, 68, 53, 93, 148, 246, 123, 2, 17, 0, 0, 0, 4, 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