Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca030df82ff91ac54a1febf7bbb17d2a15e42f300e911fcfd7c7b1d32dadc8a5

Tx prefix hash: 7831a362cdecf9df3f04b8a868cdb0227ed6a619cef9d270754de88eeffd35e6
Tx public key: fca34763d189dc4a4fa67dc47aa868c4843414d2aba4a9c13d170966f08a92b5
Timestamp: 1730628698 Timestamp [UCT]: 2024-11-03 10:11:38 Age [y:d:h:m:s]: 00:139:04:25:57
Block: 1145591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99302 RingCT/type: yes/0
Extra: 01fca34763d189dc4a4fa67dc47aa868c4843414d2aba4a9c13d170966f08a92b50211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02221595e96df8d7dbe4115478b14a87a6bb16edc782898801af72351c76aa5c 0.600000000000 1630060 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": 1145601, "vin": [ { "gen": { "height": 1145591 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02221595e96df8d7dbe4115478b14a87a6bb16edc782898801af72351c76aa5c" } } ], "extra": [ 1, 252, 163, 71, 99, 209, 137, 220, 74, 79, 166, 125, 196, 122, 168, 104, 196, 132, 52, 20, 210, 171, 164, 169, 193, 61, 23, 9, 102, 240, 138, 146, 181, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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