Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 087cd400e05a732b665488ede837376c76e06049a232e38fa241df22f455d882

Tx prefix hash: 171a3e4f99e353a7b8ba187c7e036259235803bb8a5f5d7b4565b69c46a13d4f
Tx public key: 418b004a1c87e86a915811164326091a0a44d5df308f24e8ae81fb57b643a1b8
Timestamp: 1725245400 Timestamp [UCT]: 2024-09-02 02:50:00 Age [y:d:h:m:s]: 00:245:22:20:41
Block: 1101045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175628 RingCT/type: yes/0
Extra: 01418b004a1c87e86a915811164326091a0a44d5df308f24e8ae81fb57b643a1b802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d434bc25f36f8bdc5ce4dd7a7c55d712a40d8788aa75baf49a4fac71414f2b6f 0.600000000000 1577026 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": 1101055, "vin": [ { "gen": { "height": 1101045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d434bc25f36f8bdc5ce4dd7a7c55d712a40d8788aa75baf49a4fac71414f2b6f" } } ], "extra": [ 1, 65, 139, 0, 74, 28, 135, 232, 106, 145, 88, 17, 22, 67, 38, 9, 26, 10, 68, 213, 223, 48, 143, 36, 232, 174, 129, 251, 87, 182, 67, 161, 184, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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