Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80f4e5a715705dbce1773fe16c46819b36e3d51543c261e1abee6b7eb8af9e2e

Tx prefix hash: 0df5c3b95ecc0fc3166bf7b809550bd743cb03801254b749057472faf9bfb266
Tx public key: 535be526425381efe1e77df2356be7367bdca09f800dcef418d1db70fdbc27a4
Timestamp: 1725964134 Timestamp [UCT]: 2024-09-10 10:28:54 Age [y:d:h:m:s]: 00:246:17:30:35
Block: 1107002 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176198 RingCT/type: yes/0
Extra: 01535be526425381efe1e77df2356be7367bdca09f800dcef418d1db70fdbc27a4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c492268528204dcec4bcf1b54c04dfbea0bd7731b6c5fdbf05ea98538a91ad9 0.600000000000 1584609 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": 1107012, "vin": [ { "gen": { "height": 1107002 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c492268528204dcec4bcf1b54c04dfbea0bd7731b6c5fdbf05ea98538a91ad9" } } ], "extra": [ 1, 83, 91, 229, 38, 66, 83, 129, 239, 225, 231, 125, 242, 53, 107, 231, 54, 123, 220, 160, 159, 128, 13, 206, 244, 24, 209, 219, 112, 253, 188, 39, 164, 2, 17, 0, 0, 0, 3, 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