Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2ed61309f721736a2bc7c103604aceb61dc0c89041f50340caca0b5bdaf7f78

Tx prefix hash: 884526bf3155ddbb8323893cd0f2a0cf9068c2dabc605239ccedc531df6ab3af
Tx public key: dc6c6fd183b1df43b2e7553a354b648eb970aa3b4c2903e63cabf65fc26f5342
Timestamp: 1724213964 Timestamp [UCT]: 2024-08-21 04:19:24 Age [y:d:h:m:s]: 00:224:22:34:57
Block: 1092501 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160613 RingCT/type: yes/0
Extra: 01dc6c6fd183b1df43b2e7553a354b648eb970aa3b4c2903e63cabf65fc26f534202110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8582347be13861031812143fd215c58d013541e2e110069a6e01addb48853a2 0.600000000000 1567260 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": 1092511, "vin": [ { "gen": { "height": 1092501 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8582347be13861031812143fd215c58d013541e2e110069a6e01addb48853a2" } } ], "extra": [ 1, 220, 108, 111, 209, 131, 177, 223, 67, 178, 231, 85, 58, 53, 75, 100, 142, 185, 112, 170, 59, 76, 41, 3, 230, 60, 171, 246, 95, 194, 111, 83, 66, 2, 17, 0, 0, 0, 10, 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