Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb61d9ea7fa24acfbde8a46a5e8c74aa500b5becc5cab77140ca491089d34c31

Tx prefix hash: 6e00f0f0606772e560cf8955fc5e562841f18cf9319df089ce8f5641383a0317
Tx public key: 9ba2514b7e90a8b67624b4b14e0d32a90010d4bad1ae8cccb85d6809867f3479
Timestamp: 1719200973 Timestamp [UCT]: 2024-06-24 03:49:33 Age [y:d:h:m:s]: 00:284:13:37:20
Block: 1050924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203343 RingCT/type: yes/0
Extra: 019ba2514b7e90a8b67624b4b14e0d32a90010d4bad1ae8cccb85d6809867f347902110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eeba074a0794b0dc2a782ae2024caef5be186e3af8a78ef3ded205e554d53aeb 0.600000000000 1521101 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": 1050934, "vin": [ { "gen": { "height": 1050924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eeba074a0794b0dc2a782ae2024caef5be186e3af8a78ef3ded205e554d53aeb" } } ], "extra": [ 1, 155, 162, 81, 75, 126, 144, 168, 182, 118, 36, 180, 177, 78, 13, 50, 169, 0, 16, 212, 186, 209, 174, 140, 204, 184, 93, 104, 9, 134, 127, 52, 121, 2, 17, 0, 0, 0, 1, 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