Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 235a28a6f28a9103a9513fa802ed3e372f94940b449382c211d40991139e146d

Tx prefix hash: 15288cfb40216e3a35fe625bb30dd30bf2b1cdc47e59b2bfc8f439a3ef4ab45b
Tx public key: 2de2c0de412916b4b19a49e36942bcbb0a66168a55a2087938d9a4b395482338
Timestamp: 1696797110 Timestamp [UCT]: 2023-10-08 20:31:50 Age [y:d:h:m:s]: 01:192:12:40:50
Block: 865407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398636 RingCT/type: yes/0
Extra: 012de2c0de412916b4b19a49e36942bcbb0a66168a55a2087938d9a4b39548233802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.832812808000 dcy

stealth address amount amount idx
00: cf1174c6d538c171f9766c8f4c134aa744b815bcf314d3f18caeefb707dfa4e7 0.832812808000 1319941 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": 865417, "vin": [ { "gen": { "height": 865407 } } ], "vout": [ { "amount": 832812808, "target": { "key": "cf1174c6d538c171f9766c8f4c134aa744b815bcf314d3f18caeefb707dfa4e7" } } ], "extra": [ 1, 45, 226, 192, 222, 65, 41, 22, 180, 177, 154, 73, 227, 105, 66, 188, 187, 10, 102, 22, 138, 85, 162, 8, 121, 56, 217, 164, 179, 149, 72, 35, 56, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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