Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 039841f7bf871969610fff0db25f69652672ed9a16b361800d545fd00c1be440

Tx prefix hash: 5dac22b9f573c9c9c34dd04ad370a501232d2b49199262bfd2f36bd53dbdc035
Tx public key: c6d0c58c106887a8cbe210cfe2aef2f1e7565d0e89c92a07f8bf5d2dc25daa7b
Timestamp: 1696632338 Timestamp [UCT]: 2023-10-06 22:45:38 Age [y:d:h:m:s]: 02:035:07:55:31
Block: 864025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 544877 RingCT/type: yes/0
Extra: 01c6d0c58c106887a8cbe210cfe2aef2f1e7565d0e89c92a07f8bf5d2dc25daa7b021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.841640329000 dcy

stealth address amount amount idx
00: 5d4847dd2a8d9dc7ea3ee19b4af093969c322be9df2c67fbfa298d34b1e2e158 0.841640329000 1318529 of 0

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": 864035, "vin": [ { "gen": { "height": 864025 } } ], "vout": [ { "amount": 841640329, "target": { "key": "5d4847dd2a8d9dc7ea3ee19b4af093969c322be9df2c67fbfa298d34b1e2e158" } } ], "extra": [ 1, 198, 208, 197, 140, 16, 104, 135, 168, 203, 226, 16, 207, 226, 174, 242, 241, 231, 86, 93, 14, 137, 201, 42, 7, 248, 191, 93, 45, 194, 93, 170, 123, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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