Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 898f8fb64add4e7b8fdfb239f1b2e1f2a1b7a07a0d1e916938f0a553be2ea2c7

Tx prefix hash: cf0fd5bcb789c16af83f73b64118154146a918a948c0d15f678f9061fd4e3331
Tx public key: f89824ba772b7894d9c71204d4568be359960849dfbd448047a361146e9bd838
Timestamp: 1725044337 Timestamp [UCT]: 2024-08-30 18:58:57 Age [y:d:h:m:s]: 00:120:22:22:13
Block: 1099368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86502 RingCT/type: yes/0
Extra: 01f89824ba772b7894d9c71204d4568be359960849dfbd448047a361146e9bd838021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aff285c6d29e10eebf8a276e576a7653bec9751f192e5f7d763ae6e62d811fb4 0.600000000000 1575329 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": 1099378, "vin": [ { "gen": { "height": 1099368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aff285c6d29e10eebf8a276e576a7653bec9751f192e5f7d763ae6e62d811fb4" } } ], "extra": [ 1, 248, 152, 36, 186, 119, 43, 120, 148, 217, 199, 18, 4, 212, 86, 139, 227, 89, 150, 8, 73, 223, 189, 68, 128, 71, 163, 97, 20, 110, 155, 216, 56, 2, 17, 0, 0, 0, 3, 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