Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 799e9c76c056afbd1f30d32c2dba94e0632d7599d1db0cf1bfe49254a938df70

Tx prefix hash: 35a6b0626d162e911f60ab916785fb97c4424266af6e05cc49408ea7ab6e8159
Tx public key: a3457f1b0e0f5700736387540834e6161bb1795a178e945f9b5a26097c3a619b
Timestamp: 1724353467 Timestamp [UCT]: 2024-08-22 19:04:27 Age [y:d:h:m:s]: 00:224:14:10:19
Block: 1093660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160367 RingCT/type: yes/0
Extra: 01a3457f1b0e0f5700736387540834e6161bb1795a178e945f9b5a26097c3a619b021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8f3528388e0d7281c8db14522d845473f8e64502ea42d97845dda1e83d2f9e4 0.600000000000 1568647 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": 1093670, "vin": [ { "gen": { "height": 1093660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8f3528388e0d7281c8db14522d845473f8e64502ea42d97845dda1e83d2f9e4" } } ], "extra": [ 1, 163, 69, 127, 27, 14, 15, 87, 0, 115, 99, 135, 84, 8, 52, 230, 22, 27, 177, 121, 90, 23, 142, 148, 95, 155, 90, 38, 9, 124, 58, 97, 155, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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