Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25a7ca9adfecfe45a0c5ae26d2b9f104e99e06fb66071806b6128c014c8d5f9e

Tx prefix hash: 44ef5ccfb6c79b6cd4210666cf66fd8281fe75ab927b119b7200afc798c280eb
Tx public key: 8fa8fb8d09c08d56f652cbc109641d34c2bdeaa64cac12c0dca63ea7090a1d24
Timestamp: 1700896221 Timestamp [UCT]: 2023-11-25 07:10:21 Age [y:d:h:m:s]: 01:054:12:32:25
Block: 899167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300369 RingCT/type: yes/0
Extra: 018fa8fb8d09c08d56f652cbc109641d34c2bdeaa64cac12c0dca63ea7090a1d2402110000000133af99f4000000000000000000

1 output(s) for total of 0.643704361000 dcy

stealth address amount amount idx
00: 8cc645e2eb6bf5cc6dd2a1a0a41c43edef562ffb9f772e842f2d8a7cb9fb3840 0.643704361000 1355610 of 0

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": 899177, "vin": [ { "gen": { "height": 899167 } } ], "vout": [ { "amount": 643704361, "target": { "key": "8cc645e2eb6bf5cc6dd2a1a0a41c43edef562ffb9f772e842f2d8a7cb9fb3840" } } ], "extra": [ 1, 143, 168, 251, 141, 9, 192, 141, 86, 246, 82, 203, 193, 9, 100, 29, 52, 194, 189, 234, 166, 76, 172, 18, 192, 220, 166, 62, 167, 9, 10, 29, 36, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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