Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c938061310c4353543f66941c5cbb7efb4f31dc25f67be9a95e6c54bcdd4939d

Tx prefix hash: 896633aad7f581fe69d8eebb168058ceb90821e0f1e325ccd79610c8f6918ca8
Tx public key: a27a032cfebaeba45df8d8c7c292c57a3e3390d6e5d94e85243bfa69c8dce4e1
Timestamp: 1713719279 Timestamp [UCT]: 2024-04-21 17:07:59 Age [y:d:h:m:s]: 00:207:01:37:14
Block: 1005478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148237 RingCT/type: yes/0
Extra: 01a27a032cfebaeba45df8d8c7c292c57a3e3390d6e5d94e85243bfa69c8dce4e10211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d889939d25cd9f0c65aad7e7a97b1000c10b26234514003b5d8fdf665b30b24 0.600000000000 1466184 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": 1005488, "vin": [ { "gen": { "height": 1005478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d889939d25cd9f0c65aad7e7a97b1000c10b26234514003b5d8fdf665b30b24" } } ], "extra": [ 1, 162, 122, 3, 44, 254, 186, 235, 164, 93, 248, 216, 199, 194, 146, 197, 122, 62, 51, 144, 214, 229, 217, 78, 133, 36, 59, 250, 105, 200, 220, 228, 225, 2, 17, 0, 0, 0, 4, 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