Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2a3be7016bb4f0c3a28479dfe59e3f8bc6f7a1d8228b7c13a7f653f2a117248

Tx prefix hash: c57e7ccc503fd296d567310d70ed91ef61fdb90aba3ffe39bfbf4b989efddcea
Tx public key: d1a26ddf8b464d2b0b0f4244d39fa3b462e3aaba42a5bf1083faa93457de6ded
Timestamp: 1712551271 Timestamp [UCT]: 2024-04-08 04:41:11 Age [y:d:h:m:s]: 00:217:05:20:13
Block: 995771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155525 RingCT/type: yes/0
Extra: 01d1a26ddf8b464d2b0b0f4244d39fa3b462e3aaba42a5bf1083faa93457de6ded0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9332ce2695e8b3a3da561b28db8a8467c2a97dc38a5d934eda7e4a1b931ee7e6 0.600000000000 1456185 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": 995781, "vin": [ { "gen": { "height": 995771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9332ce2695e8b3a3da561b28db8a8467c2a97dc38a5d934eda7e4a1b931ee7e6" } } ], "extra": [ 1, 209, 162, 109, 223, 139, 70, 77, 43, 11, 15, 66, 68, 211, 159, 163, 180, 98, 227, 170, 186, 66, 165, 191, 16, 131, 250, 169, 52, 87, 222, 109, 237, 2, 17, 0, 0, 0, 3, 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