Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfb4cb1d44dd7a99b26763d8bd1eed98b73bf7678057aa2b78633cb4363f3b8b

Tx prefix hash: 259801ca4b03c523361f0d2b9d79843e1133a342df8fc5b0a3a80de51580e207
Tx public key: 899411f3a6e0ea3cd058bfdb42189fe09833f08865ee24936be895893a19b3dc
Timestamp: 1720384224 Timestamp [UCT]: 2024-07-07 20:30:24 Age [y:d:h:m:s]: 00:270:04:53:19
Block: 1060739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193052 RingCT/type: yes/0
Extra: 01899411f3a6e0ea3cd058bfdb42189fe09833f08865ee24936be895893a19b3dc021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f033ecc4541c1e85af0420d275af26cd64bb83009ee4307557c894c85b53e994 0.600000000000 1531224 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": 1060749, "vin": [ { "gen": { "height": 1060739 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f033ecc4541c1e85af0420d275af26cd64bb83009ee4307557c894c85b53e994" } } ], "extra": [ 1, 137, 148, 17, 243, 166, 224, 234, 60, 208, 88, 191, 219, 66, 24, 159, 224, 152, 51, 240, 136, 101, 238, 36, 147, 107, 232, 149, 137, 58, 25, 179, 220, 2, 17, 0, 0, 0, 9, 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