Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c795458c6cef703b02c751403637c8c329d449a5c4cdf947718fd1e9c78443a3

Tx prefix hash: f5679fa25f7ad27b6dedd767697e4474a7b3917209212ac1ea47c5dab6b73c47
Tx public key: 9f02095d7fbf98012b6630ce8a40b7be0b5fb509fd743a8dababe7577e381ac5
Timestamp: 1672870988 Timestamp [UCT]: 2023-01-04 22:23:08 Age [y:d:h:m:s]: 01:332:13:16:13
Block: 667698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498689 RingCT/type: yes/0
Extra: 019f02095d7fbf98012b6630ce8a40b7be0b5fb509fd743a8dababe7577e381ac502110000000152542ceb000000000000000000

1 output(s) for total of 3.763910708000 dcy

stealth address amount amount idx
00: f46ac9b6015cabdce659024d1c838fbe1a06877b7453a6da2e86a1e9edda5eef 3.763910708000 1108913 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": 667708, "vin": [ { "gen": { "height": 667698 } } ], "vout": [ { "amount": 3763910708, "target": { "key": "f46ac9b6015cabdce659024d1c838fbe1a06877b7453a6da2e86a1e9edda5eef" } } ], "extra": [ 1, 159, 2, 9, 93, 127, 191, 152, 1, 43, 102, 48, 206, 138, 64, 183, 190, 11, 95, 181, 9, 253, 116, 58, 141, 171, 171, 231, 87, 126, 56, 26, 197, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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