Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43834e91acca590e32934c6851f6be7ba26dd6d59de19d92b895199ff34995f

Tx prefix hash: bf63d12af8a28d7e2ab0f5692b3965efe989492fe612f0820f4a39d3e512526e
Tx public key: b6cb1a75baa2646ab99bd2113739fbd1c59b425d4e6f8b3d7d50fa446d853b61
Timestamp: 1705749873 Timestamp [UCT]: 2024-01-20 11:24:33 Age [y:d:h:m:s]: 01:147:18:35:54
Block: 939388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366663 RingCT/type: yes/0
Extra: 01b6cb1a75baa2646ab99bd2113739fbd1c59b425d4e6f8b3d7d50fa446d853b6102110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12af02354d0adf69ba94a275106d1e5a18670a2f570449977363eb80c98f0a84 0.600000000000 1397496 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": 939398, "vin": [ { "gen": { "height": 939388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12af02354d0adf69ba94a275106d1e5a18670a2f570449977363eb80c98f0a84" } } ], "extra": [ 1, 182, 203, 26, 117, 186, 162, 100, 106, 185, 155, 210, 17, 55, 57, 251, 209, 197, 155, 66, 93, 78, 111, 139, 61, 125, 80, 250, 68, 109, 133, 59, 97, 2, 17, 0, 0, 0, 11, 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