Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68ee189f396ecb7ff8b6cb5c786efbee8edb556f74102ccb15bb39fe29b9a739

Tx prefix hash: a17453cf43c5ecf67d4b0bc96595104fba6b679f14b23152064814f0c6b0659f
Tx public key: 534cc08fd893b1ad0bc800d045195371cab0a95ef4cb72fea32b306e2d46aa81
Timestamp: 1711909028 Timestamp [UCT]: 2024-03-31 18:17:08 Age [y:d:h:m:s]: 00:242:01:07:46
Block: 990492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173266 RingCT/type: yes/0
Extra: 01534cc08fd893b1ad0bc800d045195371cab0a95ef4cb72fea32b306e2d46aa8102110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1988081b9bfd4e9f8c2ba95e73f87d912bcbf7dca75681e657f5f0ec87622323 0.600000000000 1450814 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": 990502, "vin": [ { "gen": { "height": 990492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1988081b9bfd4e9f8c2ba95e73f87d912bcbf7dca75681e657f5f0ec87622323" } } ], "extra": [ 1, 83, 76, 192, 143, 216, 147, 177, 173, 11, 200, 0, 208, 69, 25, 83, 113, 202, 176, 169, 94, 244, 203, 114, 254, 163, 43, 48, 110, 45, 70, 170, 129, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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